Change default behaviour of paket init to be more prescriptive
Open
Nobody has claimed this yet.
enhancement
question
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Oftentimes, my experience with Paket is something like this:
- Run
paket initon a clean repo. - Add a package from the command line e.g.
paket add Saturn. - Realise that paket by default targets all runtimes and downloaded the packages into the local folder structure.
- Modify the deps file to contain
framework: netcoreapp2.1, netstandard2.0 // or something similar
storage: none
generate_load_scripts: true // if i'm working with scripts
- Run
paket install, watch paket go through the whole resolution again and have it GC the downloaded dlls.
I wonder if there's a case for changing the default behaviour of paket init to include at least the first two, or all three, lines by default.
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 at the paket init CLI entry point and trace how it writes the deps file, comparing the current defaults with the framework, storage, and generate_load_scripts settings described here. Done means the agreed default behavior is implemented and the init/install flow no longer requires the issue’s manual edits.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- cli, devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100