Skip to content

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

Closed
3 tasks done
mtrezza opened this issue Jul 19, 2023 · 6 comments · Fixed by #2576
Closed
3 tasks done

Add relational filter conditions #2496

mtrezza opened this issue Jul 19, 2023 · 6 comments · Fixed by #2576
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

@mtrezza
Copy link
Member

mtrezza commented Jul 19, 2023

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 have

  • purchases in a Purchase class with a _User pointer field
  • transactions in a Transaction class with a _User pointer field

To filter all users who

  • made purchases of shoes (in Purchase class)
  • with a transaction using a credit card (in Transaction class)

The filter dialog could look like this:

image

Alternatives / Workarounds

n/a

@parse-github-assistant
Copy link

parse-github-assistant bot commented Jul 19, 2023

Thanks for opening this issue!

  • 🎉 We are excited about your ideas for improvement!

@mtrezza mtrezza added type:feature New feature or improvement of existing feature bounty:$100 Bounty applies for fixing this issue (Parse Bounty Program) labels Jul 19, 2023
@vardhan0604
Copy link
Contributor

vardhan0604 commented Jun 10, 2024

@mtrezza, is bounty still available for this issue?

@mtrezza
Copy link
Member Author

mtrezza commented Jun 10, 2024

@vardhan0604 sure, please feel free to go ahead and submit a PR

@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 6.0.0-alpha.9

@parseplatformorg parseplatformorg added the state:released-alpha Released as alpha version label Jul 6, 2024
vardhan0604 added a commit to vardhan0604/parse-dashboard that referenced this issue Aug 5, 2024
@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 6.0.0-beta.2

@parseplatformorg parseplatformorg added the state:released-beta Released as beta version label Oct 7, 2024
@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 6.0.0

@parseplatformorg parseplatformorg added the state:released Released as stable version label Oct 7, 2024
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
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants