ConfigurableFixerInterface::configure - param is now not nullable and not optional #3385
+28
−139
Conversation
This file contains 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
SpacePossum
approved these changes
Jan 5, 2018
|
👍 looking good. What about adding a note to the UPGRADE file? Users may need to update their config file. |
|
About config file - it is not possible to create config file that would pass null to
|
julienfalque
approved these changes
Jan 6, 2018
keradus
added a commit
that referenced
this pull request
Jan 7, 2018
…nullable and not optional (keradus) This PR was squashed before being merged into the 3.0 branch (closes #3385). Discussion ---------- ConfigurableFixerInterface::configure - param is now not nullable and not optional Commits ------- b2acbab ConfigurableFixerInterface::configure - param is now not nullable and not optional
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.
No description provided.