-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Add relational filter conditions #2496
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
Labels
bounty:$100
Bounty applies for fixing this issue (Parse Bounty Program)
state:released
Released as stable version
state:released-alpha
Released as alpha version
state:released-beta
Released as beta version
type:feature
New feature or improvement of existing feature
Comments
Thanks for opening this issue!
|
@mtrezza, is bounty still available for this issue? |
@vardhan0604 sure, please feel free to go ahead and submit a PR |
vardhan0604
added a commit
to vardhan0604/parse-dashboard
that referenced
this issue
Jun 26, 2024
2 tasks
🎉 This change has been released in version 6.0.0-alpha.9 |
vardhan0604
added a commit
to vardhan0604/parse-dashboard
that referenced
this issue
Aug 5, 2024
🎉 This change has been released in version 6.0.0-beta.2 |
🎉 This change has been released in version 6.0.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bounty:$100
Bounty applies for fixing this issue (Parse Bounty Program)
state:released
Released as stable version
state:released-alpha
Released as alpha version
state:released-beta
Released as beta version
type:feature
New feature or improvement of existing feature
New Feature / Enhancement Checklist
Current Limitation
The filter dialog in the data browser currently only allows to filter for fields in the current class. It's not possible to add a filter condition that relates to another class.
Feature / Enhancement Description
Add filter conditions that relate to other classes. Since Parse Dashboard knows the entire schema, it also knows which other classes have a pointer to the currently displayed class; it can use that information to allow for filtering by fields of these related classes.
The filter dialog could be extended with a drop-down for related classes and its fields.
Example Use Case
A user in the
_User
class may havePurchase
class with a_User
pointer fieldTransaction
class with a_User
pointer fieldTo filter all users who
Purchase
class)Transaction
class)The filter dialog could look like this:
Alternatives / Workarounds
n/a
The text was updated successfully, but these errors were encountered: