playcanvas / playcanvas/engine
Discuss console.error use in the engine and update CONTRIBUTING.md with the decision
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- JavaScript
- Stars
- 16.8k
- Forks
- 2k
- Avg merge
- 4h 32m
- Merged PRs (30d)
- 222
Description
Errors take place in the engine - asset does not load, parameter is invalid ..
I'd be good to agree on how errors should be imported, what builds (only in DEBUG?) and similar, and write up the decision into CONTRIBUTING.md.
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 reading related issue #2529 and reviewing current console.error use in the engine, then inspect CONTRIBUTING.md. The work is done when the project agrees on error-import and build behavior and the decision is documented in CONTRIBUTING.md.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100