fsprojects / fsprojects/Paket

I do not want to check in the content files received from a package--I want them on restore

Open
#2,247 1 comment 3 reactions 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

This is a feature request, not a bug. I have a couple NuGet packages that serve up a single code file as content. I would like to be able to use this content and have it always automatically dropped into place, but without having to commit the files to source.

Repro steps

Given a package foo that has content/foo.fs,

  1. paket add nuget foo project bar
  2. Edit src/bar/paket.reference and add content:true
  3. Exclude the files from your .gitignore
  4. Commit & push -- build fails
  5. Realize that's not how this feature is supposed to work right now
Expected behavior

E.g. ability to use content: on_restore in paket.reference that would copy the content in place on paket restore.

Actual behavior

The content is only placed on install.

Known workarounds

Just commit the files.

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 tracing how content from a NuGet package is handled for the content:true setting in src/bar/paket.reference, then compare that flow with paket install and paket restore. Define the content: on_restore behavior so content is copied during restore without requiring committed files, and verify the behavior against the reported reproduction steps.

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
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.