Decide on coding style and enforce mostly with PHPCS
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.7k
- Forks
- 341
- PR merge metrics
- No merged PRs in 30d
Description
Less burden on reviewers, less guess work on the contributing person (ergo me). Also automation in supporting IDEs with automatic fixing/adapting as needed.
It looks like the current code looks mostly like PSR-2. Is that intentional?
(Extracted out of https://github.com/perftools/xhgui/issues/16)
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 reviewing the current code style and comparing it with PSR-2, then investigate how PHPCS could enforce the agreed standard and support automatic fixing in IDEs. Done means the project has a decided coding style and an agreed enforcement approach; no files or tests are named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100