codex-team / codex-team/eslint-config
bad formatting in stylistic/object-curly-newline rule
Open
- Dominant language
- JavaScript
- Stars
- 7
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
What we need
What eslint needs
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the configuration for the stylistic/object-curly-newline rule and compare its current formatting behavior with the two screenshots. Confirm the intended output before changing the rule configuration; done means the resulting formatting matches the expected example.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- eslint, javascript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100