updates to use reusable workflows (#126) #5
Brennan1994Annotations
10 warnings
|
build / build:
Numerics/Mathematics/Integration/AdaptiveGuassKronrod.cs#L237
Re-throwing caught exception changes stack information (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2200)
|
|
build / build:
Numerics/Mathematics/Integration/AdaptiveGuassKronrod.cs#L192
Re-throwing caught exception changes stack information (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2200)
|
|
build / build:
Numerics/Mathematics/Integration/AdaptiveSimpsonsRule2D.cs#L176
Re-throwing caught exception changes stack information (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2200)
|
|
build / build:
Numerics/Data/Time Series/Support/TimeSeriesDownload.cs#L629
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
build / build:
Numerics/Mathematics/Integration/AdaptiveGuassKronrod.cs#L237
Re-throwing caught exception changes stack information (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2200)
|
|
build / build:
Numerics/Mathematics/Integration/AdaptiveGuassKronrod.cs#L192
Re-throwing caught exception changes stack information (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2200)
|
|
build / build:
Numerics/Mathematics/Integration/AdaptiveSimpsonsRule2D.cs#L176
Re-throwing caught exception changes stack information (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2200)
|
|
build / build:
Numerics/Data/Time Series/Support/TimeSeriesDownload.cs#L629
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
build / build:
Numerics/Data/Time Series/Support/TimeSeriesDownload.cs#L629
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
build / build
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
|