Create Parser Error/Warning Collector
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 156
- Avg merge
- 4d 43m
- Merged PRs (30d)
- 3
Description
@kewisch We touched on this briefly. I believe the idea was to have a warning collection with the optional capability of turning those warnings into errors (or the other way around) right now we throw a lot of errors.
An example of this that I ran into recently is utc offset -0000 which was assigned an error where I believe a warning would have been better. I found that Yahoo (when in etc/gmt) will return this offset. I removed the error in my development branch.
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
Start by reviewing the parser's current error handling, using the reported UTC offset -0000 case as the concrete example. Determine how warnings and errors should be collected and whether either category should be convertible into the other; done means the behavior and scope are defined and the offset case is handled accordingly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100