Tst/documentation generation upgrade #56
build.yml
on: pull_request
Building
2m 40s
Building
38s
Annotations
33 warnings
Building
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Building:
sdk/ManifestEnricher.cs#L137
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
Building:
sdk/ManifestEnricher.cs#L137
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
Building:
sdk/DTO/MessageDefinition.cs#L7
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
Building:
sdk/DefaultManifestReplacementRunner.cs#L218
The variable 'ex' is declared but never used
|
Building:
sdk/DefaultManifestReplacementRunner.cs#L287
The variable 'ex' is declared but never used
|
Building:
sdk/ManifestEnricher.cs#L48
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
Building:
sdk/ManifestEnricher.cs#L722
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
Building:
sdk/DTO/MessageDefinition.cs#L7
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
Building:
sdk/ManifestEnricher.cs#L137
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
Building:
sdk/ManifestEnricher.cs#L137
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
Building
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/upload-artifact@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Building
No files were found with the provided path: build/*. No artifacts will be uploaded.
|
Building
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.
|
Building:
sdk/ManifestEnricher.cs#L137
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
Building:
sdk/ManifestEnricher.cs#L137
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
Building:
sdk/DTO/MessageDefinition.cs#L7
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
Building:
sdk/DefaultManifestReplacementRunner.cs#L218
The variable 'ex' is declared but never used
|
Building:
sdk/DefaultManifestReplacementRunner.cs#L287
The variable 'ex' is declared but never used
|
Building:
sdk/ManifestEnricher.cs#L48
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
Building:
sdk/ManifestEnricher.cs#L722
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
Building:
src/Authentication/CryptographyHelpers.cs#L11
'RNGCryptoServiceProvider' is obsolete: 'RNGCryptoServiceProvider is obsolete. To generate a random number, use one of the RandomNumberGenerator static methods instead.' (https://aka.ms/dotnet-warnings/SYSLIB0023)
|
Building:
src/Endpoints/Results/Status202AcceptedResult.cs#L13
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
Building
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.
|
Building:
sdk/DTO/MessageDefinition.cs#L7
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
Building:
sdk/ManifestEnricher.cs#L137
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
Building:
sdk/ManifestEnricher.cs#L137
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
Building:
sdk/ManifestEnricher.cs#L48
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
Building:
sdk/DefaultManifestReplacementRunner.cs#L218
The variable 'ex' is declared but never used
|
Building:
sdk/DefaultManifestReplacementRunner.cs#L287
The variable 'ex' is declared but never used
|
Building:
sdk/ManifestEnricher.cs#L722
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
Building:
src/Endpoints/Results/Status202AcceptedResult.cs#L13
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
Building:
src/Infrastructure/EAVODataUriResolver.cs#L75
The variable 'val' is declared but never used
|