PSR规范问题
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
Research direction
The issue names no files, tests, or entry points. Start by reviewing the project's controller naming conventions and its CodeIgniter-related setup, then identify which PSR standard and affected code are in scope; done should mean the agreed PSR compliance scope is implemented and verified.
Written by the indexing model from the issue text.
Description
因CI的控制器命名方式，所以此项目未使用PSR规范
- Dominant language
- PHP
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
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.
More from FerreWagner/pathProgram
-
项目结构的分层Open
Difficulty 5/5 Over a week Newbie friendliness 20/100
All issues in FerreWagner/pathProgram
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
domain/crm-after-sales Platform(Default) priority/high
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
kind/bug status/to verify
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
PHP-CS-Fixer/PHP-CS-Fixer#9867 ·
Maintainers usually reply within 1 day
-
sync-en
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 2 days
-
sync-en
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 2 days