Use FilterInterface::getOption() from views
#7044
Merged
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
Should we deprecate it ? |
I guess we could, at least I didn't find other usages where the full options array can be required. |
Do you think it can be done in this PR or it's better in another ? |
I'll try to create a new PR for this deprecation today. |
VincentLanglet
approved these changes
Apr 13, 2021
|
What is wrong with flintci/pr ? cc @OskarStark |
jordisala1991
approved these changes
Apr 13, 2021
|
Thank you @phansys |
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.
Subject
Use
FilterInterface::getOption()from views.I am targeting this branch, because these changes respect BC.
Filter::getOptions()is not declared in the interface.Changelog