Merge paket.references with paket.dependencies

Open
#1,533 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
fsharp

Research direction

Start by comparing the existing paket.references and paket.dependencies formats described in the issue, then trace how each is handled by Paket. Done means a dependencies-file references section can represent the shown project/dependency mappings and removes the need to manage separate references files, including the stated VS/csproj use case.

Written by the indexing model from the issue text.

Description

enhancement spec

Before everyone shoots me down, hear me out...

Rather than needing to manage several references files (and add them to the csproj if you want to use it within VS etc.), why not just add a section to the dependencies file e.g.

references
   project A
      MyDependency
      MyOtherDependency
   project B
      MyDependency

Creating a new project table requires a bit of fiddling to manually create a new references file etc. - this would eliminate that.

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

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.

More from fsprojects/Paket

All issues in fsprojects/Paket

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.