[5.4] Resolved rollback not compatible with strings#18535
Merged
taylorotwell merged 1 commit intolaravel:5.4from Mar 28, 2017
Merged
[5.4] Resolved rollback not compatible with strings#18535taylorotwell merged 1 commit intolaravel:5.4from
taylorotwell merged 1 commit intolaravel:5.4from
Conversation
Contributor
Author
|
Issue ever since a refactor action: Some code was placed in a new method which does not accept strings. |
GrahamCampbell
changed the title
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
2 participants
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.
rollbackMigrationsis called fromrollbackand passes$paths, which can be astringor anarray. However,rollbackMigrationsonly accepts anarray. It's only logical that it accepts both, as the method that passes the$pathsvariable accepts both too.