-
Notifications
You must be signed in to change notification settings - Fork 258
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
Is there a way to mute NU1603? #5913
Comments
https://blog.nuget.org/20170815/Whats-nu-in-NuGet-with-VS2017-15-3.html |
is that something we can set in nuget.config? Or ar least when we add PackageReferences in memory? |
NoWarn is only read from the project file currently. |
ok but setting it in Paket.Restore.targets should work as well, right? |
Should work if you can set it before it is read. Let me know if it doesn't and we can find a different way. |
urgs. now other tools (in this case F# compiler) complain about that |
Gah! Seems like we should test these on all project types going forward. The design for this was to use the exact same fields as the compiler so that users could add these through the project properties window. |
ok reverting that for now. We need another solution. If people are using warnaserror in F# then things will crash. |
This reverts commit df69a50.
Alternatively you could set HideWarningsAndErrors to true and then replay them after restore from project.assets.json with filtering. It would be much more work than just setting nowarn however. |
O_o |
sorry, what I meant is: NuGet's current approach is not working with F# and that has nothing to do with paket. If you set the NoWarn in the project then the compiler will scream at you. |
Closing this issue in the favor of dotnet/fsharp#3626. Please feel free to reopen this if you feel otherwise. |
It's still problematic to reuse compiler features. But that's maybe just my
personal opinion.
Am 22.09.2017 20:28 schrieb "Ankit Mishra" <notifications@github.com>:
… Closing this issue in the favor of dotnet/fsharp#3626
<dotnet/fsharp#3626>.
Please feel free to reopen this if you feel otherwise.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#5913 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AADgNOL9crzl5P7-TYPLE2fZhhP-b1Ceks5sk_xbgaJpZM4Pe26j>
.
|
@forki - Hear ya. We should have communicated with more compilers than we did during 15.3. Sorry that we didn't. |
@rrelyea You should consider changing the name of the msbuild property from NoWarn to NugetNoWarn or NoWarnNuget. Kevin The C# bug:
csc Program.cs
csc Program.cs /nowarn:0219
now this:
C# ignores any non numeric value including cs0219. It is a C# bug, and it is very likely it won't get fixed. |
@KevinRansom Thanks for the detailed response. I have one correction -
Note that it is case sensitive, so |
Really capital CS works? That’s interesting … I guess I should add it to the compiler in that case.
@rrelyea apparently it is case sensitive ... so I will update the compiler to accept FS and ignore other stuff.
|
On Windows (I haven't tested this on macOS or Linux)
Install .NET Core 2.0.2
Clone fable-suave-scaffold
Instal Node LTS and Yarn latest
Run
build.cmd
Expected behaviour
No NU1603 since paket controls the dependencies
Actual behaviour
The text was updated successfully, but these errors were encountered: