Discussion - rewrite framework detection layer using Nuget.Frameworks package
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Hello! I would like to discuss a rewriting of paket framework handling layer using methods from NuGet.Frameworks package.
Currently in paket there are alot of custom logic that handles compatibility between tfms along with bunch of hardcoded custom DUs for different frameworks. I propose to not reinvent the wheel and implement logic based on code used in nuget itself.(Framework detection, comparsion and so on). What do you think, @forki ?
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 reviewing Paket's existing framework-handling logic and the NuGet.Frameworks package APIs; no file or test is named in the issue. Before implementation, establish the replacement scope and compatibility expectations with maintainers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100