Skip to content

hasMany/hasOne do not check document access authorization on resolved documents #71

Open
@eric-burel

Description

@eric-burel

Is your feature request related to a problem? Please describe.

  • We should share more code between single, multi, hasOne, and hasMany resolver, a bit like we do for mutators.
  • We need to check that hasMany/hasOne cannot be resolved on field user is not allowed to read (normally it's the case already but this deserves a unit test on its own=
  • We need to filter the list of documents user can read in relations, mainly when the permission is "owners", this is not the case yet (we however filter fields correctly in the related document)

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions