Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consume LockFileTargetLibrary for a filtered list of files the package has for a project #53

Merged
merged 1 commit into from
Aug 9, 2024

Conversation

dfederm
Copy link
Collaborator

@dfederm dfederm commented Aug 8, 2024

Previously is a package had assets which were only for a specific TF which isn't the TF that the project uses, the converter would add an exclusion of that asset type unecessarily.

This change uses the information from nuget, in particular LockFileTargetLibrary, to get a filtered view of the assets specific to what the project would actually consume.

The only hack is with analyzers, which aren't represented in LockFileTargetLibrary. Those aren't TF-specific anyway though, so we can use the "does the dir exist" mechanism for that.

Also a minor improvement is to converge inclusions and exclusions to "All" if they match everything the package contains. ie if the flags was going to be "Compile, Runtime" but that package only had those assets (no build, no analyzers, etc), then the flags is upgraded to "All".

@dfederm dfederm merged commit 9faa592 into jeffkl:main Aug 9, 2024
1 check passed
@dfederm dfederm deleted the filter-by-tf branch August 9, 2024 21:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant