fix: controller attribute filters with parameters #9769
Merged
+67
−20
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.
Description
This PR fixes an issue with controller attribute filters that use parameters. See: #9745 (comment)
Filter parameters are always declared as strings elsewhere in the framework, and there is no supported way to handle them differently. See:
To maintain consistency, this change ensures that filter parameters are treated as strings, matching the existing convention. Any other behavior would introduce inconsistency.
All existing tests have been kept, even those that may not make much sense in this context, to serve as examples of how filters handle mixed-type parameters (they are converted to strings).
This change only affects Filters - everything else will continue to behave as before.
Checklist: