Issue #140: Added explicit parameters for str_getcsv()#142
Merged
Conversation
Contributor
|
Code changes looks good to me. Tested in 501 and 405 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes issue #105.
Updated
file_search::get_id_from_csvto callstr_getcsv()with explicit parameters to fix deprecation warnings during unit tests.Environment
Testing instructions:
tool_advancedreplacetest suite:vendor/bin/phpunit --testsuite tool_advancedreplace_testsuitetool_advancedreplacewill produce the following warning (on the above environment):Expected Output from PHPUnit Tests
MOODLE_404_STABLE-issue105and re-running the testsuite: