feat: Extend model name Filter-189#247
Open
aviavissar wants to merge 1 commit into
Open
Conversation
|
🚨 Unsigned commits detected! Please sign your commits. For instructions on how to set up GPG/SSH signing and verify your commits, please see GitHub Documentation. |
aviavissar
force-pushed
the
feat-Extend-model-name-Filter-#189
branch
2 times, most recently
from
July 16, 2026 17:15
9f4f179 to
b9a7fef
Compare
Signed-off-by: aviavissar <aviavissar@gmail.com>
aviavissar
force-pushed
the
feat-Extend-model-name-Filter-#189
branch
from
July 16, 2026 17:22
b9a7fef to
81e9a81
Compare
This file contains hidden or 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
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.
What type of PR is this?
What this PR does / why we need it:
we should extend the modelname Filter to be called something like ByField, with configuration of fieldName and optionalValues.
Which issue(s) this PR fixes:
Fixes #
Release note (write
NONEif no user-facing change):