Standardize error messages
Open
Nobody has claimed this yet.
discussion
- Dominant language
- PHP
- Stars
- 3.5k
- Forks
- 468
- Avg merge
- 3h 9m
- Merged PRs (30d)
- 2
Description
Right now the error messages that are thrown are pretty messy.
We should standardize them to make them more predictable and uniform.
- Should we terminate messages with a dot
.? - How do we quote things like class names? Backticks, Single or double quotes, square brackets, not at all?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name files, tests, or an entry point. First review the project's existing error messages and decide on consistent punctuation and quoting conventions. Done means the conventions are agreed and applied consistently, with coverage for the affected messages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, laravel, php
- Domain
- api, backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100