Resolve "Make GraphQL/Graphene mutations actually return error messages"
Merged
requested to merge 832-make-graphql-graphene-mutations-actually-return-error-messages into release-3.0
All threads resolved!
Closes #832 (closed)
Merge request reports
Activity
added type::bug label
assigned to @yuha
- Resolved by Hangzhi Yu
added 71 commits
-
fa71754e...743f4360 - 71 commits from branch
release-3.0
-
fa71754e...743f4360 - 71 commits from branch
added 1 commit
- 69764d5b - Use workaround for actually showing errors occuring in GraphQL mutations
added 1 commit
- df9152fc - Use custom GraphQL execution context that logs exceptions
added 30 commits
-
df9152fc...6f2d6890 - 29 commits from branch
release-3.0
- 4f388118 - Use custom GraphQL execution context that logs exceptions
-
df9152fc...6f2d6890 - 29 commits from branch
- Resolved by magicfelix
- Resolved by magicfelix
- Resolved by magicfelix
I wonder where this code comes from. I somehow have some doubts that it is entirely original work…
added 1 commit
- 443f2f30 - Use custom GraphQL execution context that logs exceptions
added 1 commit
- d5732776 - Use custom GraphQL view context that logs exceptions
added 1 commit
- 027a6cb4 - Use custom GraphQL view context that logs exceptions
- Resolved by magicfelix
added 1 commit
- 8320f4da - Use custom GraphQL view context that logs exceptions
added 19 commits
-
8320f4da...e9f24856 - 18 commits from branch
release-3.0
- 84c3f1d8 - Use custom GraphQL view context that logs exceptions
-
8320f4da...e9f24856 - 18 commits from branch
mentioned in commit 5ee2b63c
mentioned in commit 7d00576f
Please register or sign in to reply