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

Should permissions.conditions apply to associations? #90

Open
wants to merge 2 commits into
base: develop
Choose a base branch
from

Conversation

charlie-s
Copy link

Given these rules:

{
  rules: {
    fetch: [
      {
        model: 'User',
        fields: [],
        associations: [],
        conditions: [
          { field: 'tenantId', value: ':ctx.state.user.tenantId' }
        ]
      },
      {
        model: 'Role',
        fields: [],
        associations: [],
        conditions: []
      },
    ]
  }
}

and this Graphql query:

query {
  UserCurrent { // custom query that returns the current user
    id
    name
    Roles {
      id
      name
    }
  }
}

when the Roles association is loaded, the generated SQL includes where Role.tenantId = X, which of course doesn't exist on that model.

It could be as simple as adding the !isAssociation check like in this PR, but should it be going a step further and looking for any conditions defined in permissions.rules for the associated model?

For example, if you had

{
  model: 'Role',
  fields: [],
  associations: [],
  conditions: [
    { field: 'active', value: true }
  ]
}

you'd probably want this condition to run as well.

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.

1 participant