Improve extended debug messsaging logic
Open
Nobody has claimed this yet.
cleanup/refactoring
- Dominant language
- JavaScript
- Stars
- 7
- Forks
- 7
- Avg merge
- 9h 4m
- Merged PRs (30d)
- 22
Description
At the moment, there are multiple places in converter.js that use the following structure:
if (debugExtended.enabled) {
debug(`(buildRelationQuery) ...`);
}
This could be extracted to a method like debug(extended) to avoid having if's in multiple
places.
Related discussion
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 in converter.js by locating the repeated debugExtended.enabled checks and read the related discussion in pull request 18. Consolidate the repeated conditional behavior behind the proposed debug(extended) method, then verify that extended debug messages still appear when enabled and remain suppressed otherwise.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100