Schema change based on user permissions about directus

[br41nslug]

Looks like you're trying to create a new "mission" with a specific ID which logically fails if you dont have permission to do so. The error is pretty on-point there, you cannot assign an object (non-int) to an integer field:

mutation Update_executed_post_item {
    update_executed_post_item(
        id: "25"
        data: { adjustements: [{ title: "missing tool", mission_id: 25 }] }
    ) {
        id
    }
}

Closing this issue for now since it looks to be an invalid payload for the permissions you've set. Happy to re-open if that is not the case.

[alexdess]

I agree that if the user does not have creation/modification rights, then they should only populate mission_id.

However, in this perspective, populating only the ID should also work for a user with modification rights, which is not currently the case, and another exception is raised. This is why GraphQL types "change" depending on the rights, which I believe is a problem.

The query is accepted

After, I add the modification right

The same request doesn't work anymore