jprichardson / jprichardson/node-logmeup
Descriptive error if logmeup.json can't be parsed.
Open
Nobody has claimed this yet.
- Dominant language
- CoffeeScript
- Stars
- 2
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Currently makes it look like a bug in logmeup if the config file is invalid JSON.
Contributor guide
No contributing guide indexed for this repository
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 locating where logmeup.json is read and where invalid JSON currently surfaces. Reproduce the problem with malformed JSON, then make the resulting error clearly identify the configuration file and parsing failure. Verify the behavior with the repository's existing tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- coffeescript, node.js
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100