Add option for comparing NuGet structure and NuGet metadata. #17
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, we use
api-tools
in AndroidX and GooglePlayServices repositories to help us verify changes to C# APIs when we make binding changes.However, there are some additional scenarios we would like to verify changes to:
<title>
or<description>
.targets
file doesn't disappearThese additional checks will help give us more confidence to update our project file templates without silently breaking packages.
Implemented as a new option:
If there are changes to NuGet metadata or contents, this will produce a file called
nuget-diff.md
in the output directory. This file looks like: