Revert "Remove link to altinn-din from app-template" #369
tjololotest-and-analyze.yml
on: pull_request
Static code analysis
5m 43s
Annotations
16 warnings
|
Static code analysis:
src/App.IntegrationTests/Mocks/Services/DataMockSI.cs#L91
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.
|
|
Static code analysis:
src/App.IntegrationTests/Mocks/Services/DataMockSI.cs#L204
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.
|
|
Static code analysis:
src/App.IntegrationTests/Mocks/Services/DataMockSI.cs#L231
'IAppResources.GetApplication()' is obsolete: 'GetApplication is scheduled for removal. Use Altinn.App.Core.Internal.App.IAppMetadata.GetApplicationMetadata instead'
|
|
Static code analysis:
src/App.IntegrationTests/ApiTests/ProcessApiTest.cs#L171
Do not use Assert.True(false, message) to fail a test. Use Assert.Fail(message) instead.
|
|
Static code analysis:
src/App.IntegrationTests/Mocks/Services/DataMockSI.cs#L91
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.
|
|
Static code analysis:
src/App.IntegrationTests/Mocks/Services/DataMockSI.cs#L204
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.
|
|
Static code analysis:
src/App.IntegrationTests/Mocks/Services/DataMockSI.cs#L231
'IAppResources.GetApplication()' is obsolete: 'GetApplication is scheduled for removal. Use Altinn.App.Core.Internal.App.IAppMetadata.GetApplicationMetadata instead'
|
|
Static code analysis:
src/App.IntegrationTests/ApiTests/ProcessApiTest.cs#L171
Do not use Assert.True(false, message) to fail a test. Use Assert.Fail(message) instead.
|
|
Static code analysis:
src/App.IntegrationTests/Mocks/Services/DataMockSI.cs#L91
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.
|
|
Static code analysis:
src/App.IntegrationTests/Mocks/Services/DataMockSI.cs#L204
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.
|
|
Static code analysis:
src/App.IntegrationTests/Mocks/Services/DataMockSI.cs#L231
'IAppResources.GetApplication()' is obsolete: 'GetApplication is scheduled for removal. Use Altinn.App.Core.Internal.App.IAppMetadata.GetApplicationMetadata instead'
|
|
Static code analysis:
src/App.IntegrationTests/ApiTests/ProcessApiTest.cs#L171
Do not use Assert.True(false, message) to fail a test. Use Assert.Fail(message) instead.
|
|
Static code analysis:
src/App.IntegrationTests/Mocks/Services/DataMockSI.cs#L91
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.
|
|
Static code analysis:
src/App.IntegrationTests/Mocks/Services/DataMockSI.cs#L204
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.
|
|
Static code analysis:
src/App.IntegrationTests/Mocks/Services/DataMockSI.cs#L231
'IAppResources.GetApplication()' is obsolete: 'GetApplication is scheduled for removal. Use Altinn.App.Core.Internal.App.IAppMetadata.GetApplicationMetadata instead'
|
|
Static code analysis:
src/App.IntegrationTests/ApiTests/ProcessApiTest.cs#L171
Do not use Assert.True(false, message) to fail a test. Use Assert.Fail(message) instead.
|