-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
WebAssembly.Sdk - Unsuppressable warnings #78690
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsDescriptionWhen building a Blazor WASM app with SQLite NuGet package, I get a warning about Reproduction Steps
Expected behaviorNo warnings about native libraries, or some way to suppress them. Actual behavior
Regression?No response Known WorkaroundsNo response Configuration
Other informationThe warnings does not contain any message code that could be used for suppression (e.g. CS1234). The message also spans multiple lines, which each are counted as separate warnings.
|
@maraf this needs warning numbers, same as what you added for runtime/src/tasks/WasmAppBuilder/IcallTableGenerator.cs Lines 156 to 157 in 2ae7f5d
And we can add this for any other warnings that we generate from the task. |
Description
When building a Blazor WASM app with SQLite NuGet package, I get a warning about
Found a native function (sqlite3_config) with varargs in e_sqlite3
.Reproduction Steps
dotnet new blazorwasm-empty
dotnet add package SQLitePCLRaw.bundle_e_sqlite3
dotnet build
Expected behavior
No warnings about native libraries, or some way to suppress them.
Actual behavior
Regression?
No response
Known Workarounds
No response
Configuration
Other information
The warnings does not contain any message code that could be used for suppression (e.g. CS1234). The message also spans multiple lines, which each are counted as separate warnings.
The text was updated successfully, but these errors were encountered: