Improve config validation + fix `outputGlob`
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 816
- Forks
- 88
- PR merge metrics
- No merged PRs in 30d
Description
There are various elements of the lage config that would benefit from improved validation--like certain properties that are optional, but cause very unexpected behavior if not set (example: outputGlob, see #878). Ideally this should be improved at some point, but would probably need to be in a major version.
outputGlob issue
Fix merging issue called out here so that outputGlob respects the documented default lib/**/*
https://github.com/microsoft/lage/pull/878#issuecomment-3849159888
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.
Research direction
Start by tracing the lage config merge behavior for outputGlob, using the behavior described in issue #878 and the documented default lib/**/* as the reference. Check how optional config properties are validated, and consider the work complete when outputGlob preserves that default and the relevant validation behavior is covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100