Open sbor23 opened 4 years ago
It's not as grave is I feared, the specific issue we're facing is tracked here: https://github.com/graphql-python/graphene-django/issues/906
But we should still consider trying to upstream the changes mentioned in said docstrings, the issues on graphene-django are all stale although solutions have been posted.
Our
Mutation
is a homebrew solution to fix some issues with the graphene-djangoClientIDMutation
. Now I don't know all the background of this, but https://github.com/projectcaluma/caluma/pull/985 shows that we are running into issues with this now, because it seems like theSaveDocumentInput
InputType doesn't know about the id which is passed. See https://travis-ci.com/github/projectcaluma/caluma/jobs/343595361#L2099The
Mutation
links three upstream issues that led to the custom implementation: https://github.com/projectcaluma/caluma/blob/master/caluma/caluma_core/mutation.py#L79Should be considered a show-stopper for https://github.com/projectcaluma/caluma/issues/814
Who knows enough about the graphene internals to tackle this?