Improve definition of filterables fields #39
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.
Hi. Here is me again... 🤣
in my project I wanted to define filterable fields type, but there was no option to do it. So I improved parsing of given values:
TypedFilterInterface
, with methodgetType()
, that should return wished input type. This type will be used, if instance of class that implementsTypedFilterInterface
defined inYourDefinition::getFilterables()
So here are all possible definitions of filterables:
I also updated README and listed there all possible usages (as above).
There is NO breaking changes. Old definitions are still working, with default
Type::json()
type.As this is already 4th pull request, after merging some of PRs may require manually merge from me. So... let me know...