[RFC] JSON package / library config info output
Nobody has claimed this yet.
- Dominant language
- Lean
- Stars
- 9.2k
- Forks
- 990
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 175
Description
Processing lakefile.lean is a nontrivial cost (~200ms) and a minimum requirement to do anything with lake packages. I think it would be good for lake to generate a parsed version of (some of) the information in a package configuration and stick it somewhere in the build directory, along with a trace so that it is easy to determine if the information is out of date. Then many activities with package management can be handled by reading the JSON file instead of the lakefile, using the trace to determine whether to call lake to refresh the contents of the file. (This could also be part of lake-manifest.json.)
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 with the code that processes lakefile.lean, then compare the information currently represented by lake-manifest.json. Establish the JSON schema, where the build-directory output and freshness trace belong, and whether this should extend lake-manifest.json; done requires an agreed design and implementation scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100