fsprojects / fsprojects/Paket

Add WARNING logs for the scenario where target framework and paket group versions don't match.

Open
#3,365 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
F#
Stars
2.1k
Forks
528
Avg merge
1d 12m
Merged PRs (30d)
54

Description

Description

Please provide a succinct description of your issue.
If the target framework is netcoreapp2.0, but the paket group Netstandard restrict to >= netcoreapp2.1, dependencies do not get resolved. This is expected, but having some WARNING logs pointing out that this is the issue would make it easy to troubleshoot the situation.

Repro steps

Please provide the steps required to reproduce the problem

  1. Step A
    Use target framework: netcoreapp2.0.
    Create paket group that's restricted to >= netcoreapp2.1

  2. Step B
    Run paket install.

Expected behavior

Compilation attempt (dotnet build) should fail, by printing logs that say: paket group restriction is too tight for the dependencies being resolved.

Actual behavior

Compilation attempt fails with no relevant logs.

Known workarounds

Please provide a description of any known workarounds.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the scenario with target framework netcoreapp2.0, a Paket group restricted to >= netcoreapp2.1, and paket install; compare the output with the expected dependency-resolution failure. Trace the resolution and logging entry points reached by this command, and consider the work done when a clear WARNING identifies the framework and Paket group version mismatch.

Written by the indexing model from the issue text.

Assessment

Tech stack
fsharp
Domain
cli, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
64/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.