improve use case of `restore` that would not restore anything due to framework restriction and project being with wrong/lower framework version
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Just taking a note that we should look at improving the case where paket.dependencies / paket.lock have a framework restriction, and projects get strictly 0 packages restored.
The use case is this commit: https://github.com/roboz0r/fable-elmish-lit-tailwind/commit/c549d767a2b855e0d2e18274fa081c3e37622a52
which requires the fixes up to this commit
https://github.com/smoothdeveloper/fable-elmish-lit-tailwind/commit/5b7c5d7bbaa2bd791084cfdb475b8139d5bfa73f
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 comparing the referenced commits and inspect the paket.dependencies and paket.lock framework restrictions. Reproduce the case where a project with the wrong or lower framework version restores zero packages, then determine the expected restore behavior and add coverage for it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100