dapr
/
dotnet-sdk
mirror of https://github.com/dapr/dotnet-sdk.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Removed one of the options for suppression since I had no luck with it in the code generator tests 

Signed-off-by: Whit Waldo <whit.waldo@innovian.net>
This commit is contained in:
Whit Waldo 2025-06-21 04:38:22 -05:00
parent f765bf3d53
commit dd375db928
1 changed files with 2 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
daprdocs/content/en/dotnet-sdk-docs/dotnet-development/dotnet-development-experimental-attributes.md
View File

@ -75,24 +75,7 @@ var client = new DaprEncryptionClient();
This approach is useful when you want to suppress warnings only for specific sections of your code. This approach is useful when you want to suppress warnings only for specific sections of your code.
#### Option 2: Using SuppressMessage attribute #### Option 2: Project-level suppression
For a more targeted approach, you can use the `[SuppressMessage]` attribute:
```csharp
using System.Diagnostics.CodeAnalysis;
[SuppressMessage("Experimental", "DAPR_CRYPTOGRAPHY:Type is experimental", Justification = "Intentionally using experimental Cryptography API")]
public void MyMethod()
{
var client = new DaprEncryptionClient();
// Your code
}
```
This approach is more declarative and provides documentation about why you're suppressing the warning.
#### Option 3: Project-level suppression
To suppress warnings for an entire project, add the following to your `.csproj` file. To suppress warnings for an entire project, add the following to your `.csproj` file.
file. file.
@ -113,7 +96,7 @@ You can include multiple diagnostic IDs separated by semicolons:
This approach is particularly useful for test projects that need to use experimental APIs. This approach is particularly useful for test projects that need to use experimental APIs.
#### Option 4: Directory-level suppression #### Option 3: Directory-level suppression
For suppressing warnings across multiple projects in a directory, add a `Directory.Build.props` file: For suppressing warnings across multiple projects in a directory, add a `Directory.Build.props` file: