Nuget build errors and formatter for variable assignment SET statement #36
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
September 6, 2024 13:32
…st in the package" and NU5040: "The readme file 'readme.md' is empty."
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Hello, thanks very much for your project!
I found that it would not build under VS2022 without adding references in 3 project files to the existing readme.md files and making sure those were not empty files:
NU5039: The readme file 'readme.md' does not exist in the package.
NU5040: The readme file 'readme.md' is empty.
I then added formatting support for the variable assignment SET statement, by copying and editing an existing example. The parser already had support for SET.
Cheers
Nick