ash-project / ash-project/ash_graphql
2.0: Align placement of erros between generic and other actions
Open
- Dominant language
- Elixir
- Stars
- 97
- Forks
- 102
- Avg merge
- 12h 51m
- Merged PRs (30d)
- 5
Description
Seems like currently default placement for errors in in a result. Except for generics, they put errors at the top level by default.
Makes sense to align them to the same default in next Ash version.
Contributor guide
Research direction
Start by comparing the default error placement for generic actions with the placement used by other actions in the GraphQL results. Trace the relevant defaults and existing coverage, then confirm that both paths produce errors at the same level in the next Ash version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir, graphql
- Domain
- api, backend-api-design
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100