-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Optionally comparing fields in Var.contains, e.g. on rx.Base based types. #3375
Merged
masenf
merged 7 commits into
reflex-dev:main
from
abulvenz:contains-optionally-using-object-field-comparison
May 25, 2024
Merged
Changes from 3 commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
d22640c
feat: Optionally comparing fields, e.g. on rx.Base based types.
abulvenz fede69f
feat: Minimally invasive change.
abulvenz 25e11f8
fix: Supporting old-school python versions.
abulvenz d2b3982
Merge remote-tracking branch 'upstream/main' into contains-optionally…
abulvenz acaf31b
Merge remote-tracking branch 'upstream/main' into contains-optionally…
abulvenz 9b22686
fix: Adding masenf's suggestions to use var instead of string.
abulvenz bdd1434
Merge remote-tracking branch 'upstream/main' into contains-optionally…
abulvenz File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i think this should work if the field is specified as a state var, so maybe we can write it like
and
f"{self._var_name}.some(e=>e[{field._var_full_name}]==={other._var_full_name})"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@masenf Thanks for your idea. I tried it as you suggested:
The code results in this for string literals passed in
where key is not defined ⚡.
Maybe it would be helpful for me to understand the aim of your suggested change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the purpose is being able to write something like
where you can change the value of
filter_key
dynamicallyThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah okay, we actually need
_var_name_unwrapped
, like thisThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @masenf, I will use your corrected version, it works with both strings and vars.
One thing that is that
e.{field}
could also take nested values likefield="address.street"
which will not work with thee[...]
syntax.I can also support this case, when I use this abomination:
Then you could write:
But at some point it becomes ridiculously complex...
-------- 8< --------- 8< --------------
And ideas for sleepless nights 🛌 🖥️
Please nobody take this seriously 😄
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🏆