Skip to content
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

Junction filters #40

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

singingwolfboy
Copy link
Contributor

@singingwolfboy singingwolfboy commented Nov 5, 2019

This implements basic junction table filtering for many-to-many connections, in the same way that PgConnectionArgCondition does. By default, this filtering arg is named junctionCondition, and is managed separately from the condition arg. However, if the developer adds a @manyToManyCombinedConditionArg smart comment to the constraint, the filters for the junction table and the right table will be combined in the condition arg (and duplicated filterable columns will result in an error).

This pull request depends on #43, and is rebased on top of it.

@benjie
Copy link
Member

benjie commented Nov 13, 2019

(v4.5.0-rc.0 is now out.)

@mattbretl
Copy link
Member

This is great, thanks! I'm hesitating to merge only because filtering functionality tends to be a slippery slope (as I know all too well 😉 ). I'm also not sure it should be exposed by default.. on some of my own projects I've excluded the core PgConnectionArgCondition plugin and replaced it with the filter plugin, and I would probably exclude junctionCondition as well. How do you feel about maintaining this separately?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants