frostney / frostney/GocciaScript
Migrate toolchain to lwpt
Nobody has claimed this yet.
- Dominant language
- Pascal
- Stars
- 20
- Forks
- 3
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 45
Description
Adopt lwpt (Path A) as the project toolchain: migrate build/format/test/dependency management onto lwpt build/format/test/install, and dedup the in-repo toml/semver/cli/testing implementations onto lwpt workspace packages. Scheduled after the performance and conformance work.
Contributor 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.
Research direction
Start by reviewing the project's current build, format, test, and dependency-management entry points, then compare them with the corresponding lwpt build/format/test/install commands and workspace packages. Done means those workflows use lwpt and the in-repository toml, semver, CLI, and testing implementations are deduplicated, after the scheduled performance and conformance work.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100