Reorder static checks by performance and warning probability
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
Research direction
The checkStatic function in runTests.sh and the check:static script in composer.json each call the same set of static checks. Read both to see the current order, then reorder them to match the sequence listed in the issue. Done when both lists run in the proposed order and the script still exits non-zero on the first failing check.
Written by the indexing model from the issue text.
Description
Story
As a developer, I want the checkStatic script from runTests.sh and the check:static Composer script to run the scripts in an order that has faster checks first and checks that tend to catch problems more often first so that I can work faster and have less irrelevant output.
Acceptance criteria
- The scripts called by the
checkStaticscript are sorted as listed below. - The scripts called by the
check:staticComposer script are sorted as listed below.
Additional information
Proposed order:
lintPhp &&
cgl &&
phpstan &&
rector &&
composerNormalize &&
lintTypoScript &&
lintYaml &&
lintJson &&
checkIntegrityXliff &&
normalizeXliff &&
psrVerify &&
composerUnused
- Dominant language
- PHP
- Stars
- 92
- Forks
- 34
- Avg merge
- 12h 23m
- Merged PRs (30d)
- 78
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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 TYPO3BestPractices/tea
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 88/100
TYPO3BestPractices/tea#2460 ·
Maintainers usually reply within 1 day
-
github_actions
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
TYPO3BestPractices/tea#2458 ·
Maintainers usually reply within 1 day
-
github_actions
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
TYPO3BestPractices/tea#2457 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
TYPO3BestPractices/tea#2117 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 Half a day Newbie friendliness 35/100
TYPO3BestPractices/tea#2393 ·
Maintainers usually reply within 1 day
All issues in TYPO3BestPractices/tea
Similar issues
-
sync-en
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/blocks-engine#4621 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
YunoHost-Apps/snappymail_ynh#205 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Automattic/static-site-importer#2653 ·
Maintainers usually reply within 1 day
-
Bug (unconfirmed) Search :mag:
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
FreshRSS/FreshRSS#9533 · 1 reaction ·
Maintainers usually reply within 1 day