Multiple filters for a route and classname filter #5128
Merged
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
Supersedes #5108
Config\Feature
class for enabling multiple filtersCI4 follows semantic versioning, so changes that break backward compatibility are not allowed without major version up.
The multiple filters feature breaks backward compatibility, because it uses new methods.
Therefore, it is disabled by default and users can enable it in the configuration class if they want to use it.
Users who want to use the new features will be able to set themselves up for disruptive changes.
Users of existing CI4 applications will be backward compatible through updates.
The code will be more complex, but I think it will be less complex than adding code that forces the API to handle values of different types (e.g. converting an
array
to CSV and set it to astring
variable) on the condition that no API changes are made at all.Checklist: