Update process name check in CustomResourceDefinitionGenerator #83
marcusbooyahAnnotations
10 warnings
|
build
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-dotnet@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
build
Some target frameworks declared in the dependencies group of the nuspec and the lib/ref folder do not have exact matches in the other location. Consult the list of actions below:
|
|
build
- Add lib or ref assemblies for the netstandard2.0 target framework
|
|
build:
src/Neon.Operator.Analyzers/Generators/CustomResourceDefinitionGenerator.cs#L41
The using directive for 'Microsoft.CodeAnalysis' appeared previously in this namespace
|
|
build:
src/Neon.Operator.Analyzers/Generators/CustomResourceDefinitionGenerator.cs#L41
The using directive for 'Microsoft.CodeAnalysis' appeared previously in this namespace
|
|
build:
test/Test.Analyzers/Test_AppExtensions.cs#L40
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.
|
|
build:
test/Test.Analyzers/Test_AppExtensions.cs#L89
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.
|
|
build:
src/Neon.Operator.Analyzers/Generators/CustomResourceDefinitionGenerator.cs#L41
The using directive for 'Microsoft.CodeAnalysis' appeared previously in this namespace
|
|
build:
test/Test.Analyzers/Test_AppExtensions.cs#L40
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.
|
|
build:
test/Test.Analyzers/Test_AppExtensions.cs#L89
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.
|