Write missing tests.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Search the repository for @TODO markers and inspect the referenced composer plugin classes, paying attention to their static usage. Run the existing test suite first; done means each identified TODO has an appropriate test and the suite passes.
Written by the indexing model from the issue text.
Description
Check the code for @TODO markers.
Some of the tests may be tricky to write given how composer plugin classes are usually used statically.
- Dominant language
- PHP
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 loadsys/composer-plugins
-
enhancement help wanted
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
enhancement help wanted
Difficulty 4/5 3-5 days Newbie friendliness 30/100
loadsys/composer-plugins#1 · 1 comment ·
All issues in loadsys/composer-plugins
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
UX
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ProfessionalWiki/NeoWiki#1573 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
endoflife-date/endoflife.date#11194 ·
Maintainers usually reply within 1 day