kowainik / kowainik/github-graphql
Custom error messages for types
- Dominant language
- Haskell
- Stars
- 7
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Similar to the `Repository` type. Messages probably will have the same structure, so maybe it makes sense to have a helper type family that takes several arguments and builds the message from them.
The following types currently lack custom error messages:
- [x] RepositoryArgs
- [ ] IssuesArgs
- [ ] PullRequestsArgs
- [ ] CreateIssueInput
- [ ] IssueOrder
- [ ] LabelsArgs
- [ ] AssigneesArgs
Contributor guide
Research direction
Start by examining the existing custom error messages for the Repository type and compare their structure with the listed unchecked types. Implement the agreed message handling for IssuesArgs, PullRequestsArgs, CreateIssueInput, IssueOrder, LabelsArgs, and AssigneesArgs; done means each listed type has a custom error message consistent with Repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, haskell
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100