codecombat / codecombat/codecombat
Warn when using conflicting Components
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 8.6k
- Forks
- 4.2k
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 39
Description
Sometimes, while writing the code, the code doesn't see anything after this.getNearestEnemy(); and stops there.
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 reproducing the reported behavior around this.getNearestEnemy() and inspect how conflicting Components are handled. Identify the relevant component or game-code entry point from the reproduction, then determine what warning should appear and how completion can be verified. No file or test is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- game-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100