croct-tech / croct-tech/coding-standard-js
Enable member-ordering rule
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
✨ Feature request
Enable the member-ordering rule from typescript-eslint
Motivation
We should keep the order of the members consistent between our declarations and between our languages.
Alternatives
Additional context
For PHP and Java we have:
- Static fields
- Instance fields
- Constructor(s)
- Static public methods
- Instance methods
- Static private methods
We should define the order for public, protected and private between the fields and instance methods
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 reading the linked typescript-eslint member-ordering rule documentation and the repository's existing ESLint configuration. Define the ordering for static and instance members, visibility levels, constructors, fields, and methods to match the stated PHP and Java conventions. Done means the rule is enabled with an agreed, consistent ordering.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- eslint, typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100