Pass linting checks
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Read the linked v3 linting specification and inspect the track's GitHub Actions workflow. Run ./bin/fetch-configlet or ./bin/fetch-configlet.ps1, then run ./bin/configlet lint locally to identify the current v3 violations. Done means the track passes all checks defined by configlet lint.
Written by the indexing model from the issue text.
Description
This issue is part of the migration to v3. You can read full details about the various changes here.
The configlet tool has a lint command that checks if a track's configuration files are properly structured - both syntactically and semantically. Misconfigured tracks may not sync correctly, may look wrong on the website, or may present a suboptimal user experience, so configlet's guards play an important part in maintaining the integrity of Exercism.
We're updating configlet to work with v3 tracks, which have a different set of requirements than v2 tracks.
The full list of rules that will be checked by the linter can be found in this spec.
⚠ Note that only a subset of the linting rules has been implemented at this moment. This means that while your track may be passing the checks at this moment, it might fail later. We thus strongly suggest you keep this issue open until we let you know otherwise.
Goal
Ensure that the track passes all the (v3 track) checks defined in configlet lint.
To help verify that the track passes all the linting rules, the v3 preparation PR has added a GitHub Actions workflow that automatically runs configlet lint.
It is also possible to run configlet lint locally by running the ./bin/fetch-configlet (or ./bin/fetch-configlet.ps1) script to download a local copy of the configlet binary. Once downloaded, you can then do ./bin/configlet lint to run the linting on your own machine.
Tracking
- Dominant language
- PureScript
- Stars
- 38
- Forks
- 35
- PR merge metrics
- No merged PRs in 30d
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.
More from exercism/purescript
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
exercism/purescript#235 · 3 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
exercism/purescript#220 · 7 comments · 1 reaction ·
-
x:action/improve x:knowledge/none x:size/small x:type/content
Difficulty 4/5 3-5 days Newbie friendliness 25/100
exercism/purescript#216 ·
-
Build analyzer Openx:action/create x:knowledge/advanced x:module/analyzer x:size/massive x:type/coding
Difficulty 5/5 Over a week Newbie friendliness 20/100
exercism/purescript#215 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
exercism/purescript#202 ·
All issues in exercism/purescript
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
copse-dev/agent-pane#2953 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
simonw/sqlite-utils#872 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
danielmiessler/LifeOS#2215 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·