Point the verification docs at the package README instead of its lessons page
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- markdown
- Domain
- documentation
Research direction
The links to change are in docs/verification/automation.md, docs/verification/README.md and AGENTS.md, which currently point at lessons.md on main. Do not start until nemchik/suitescript-verify#13 is released and this repo pins that version. Then repoint each link to the installed package README and run npm test to confirm the link checks pass.
Written by the indexing model from the issue text.
Description
Problem
docs/verification/automation.md and AGENTS.md tell agents to read the package's docs/verification/lessons.md on main. That link is not versioned with the pinned suitescript-verify dependency, so the guidance can change under us.
The package will move the lessons into its README so they ship with each version: nemchik/suitescript-verify#13.
Acceptance criteria
- nemchik/suitescript-verify#13 is released and this repo pins that version.
-
docs/verification/automation.md,docs/verification/README.mdand AGENTS.md point to the package README (the installed version), notlessons.mdonmain. -
npm testlink checks pass.
Blocked by nemchik/suitescript-verify#13. Part of the later tidy of agent knowledge for the package split.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- Avg merge
- 2h 8m
- Merged PRs (30d)
- 64
Getting set up
- No Dockerfile or Docker Compose file
- Has a 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 nemchik/biome-plugin-suitescript
-
ready-for-agent
Difficulty 1/5 1-3 hours Newbie friendliness 72/100
nemchik/biome-plugin-suitescript#137 ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
nemchik/biome-plugin-suitescript#87 ·
Maintainers usually reply within 1 day
-
enhancement ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
nemchik/biome-plugin-suitescript#48 ·
Maintainers usually reply within 1 day
-
ready-for-agent
Difficulty 3/5 Half a day Newbie friendliness 45/100
nemchik/biome-plugin-suitescript#138 ·
Maintainers usually reply within 1 day
-
ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
nemchik/biome-plugin-suitescript#136 ·
Maintainers usually reply within 1 day
All issues in nemchik/biome-plugin-suitescript
Similar issues
-
parse: child keys like `007`, `1e3`, `0x1f`, `-1` make the parent an empty array and hide the valueOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement follow-up
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
bketelsen/pi-pocket-team#232 ·
Maintainers usually reply within 1 day
-
bug UI
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
wardian-app/Wardian#1746 ·
Maintainers usually reply within 1 day
-
area: interop area: sip-core v3
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
fonoster/routr#705 · 1 comment ·
Maintainers usually reply within 1 day