Validate MiniLcm types #252
Annotations
5 errors and 11 warnings
|
Dotnet build:
backend/FwLite/LcmCrdt/CrdtMiniLcmApi.cs#L144
'MiniLcmValidators' does not contain a definition for 'ValidateAndThrowAsync' and the best extension method overload 'DefaultValidatorExtensions.ValidateAndThrowAsync<SemanticDomain>(IValidator<SemanticDomain>, SemanticDomain, CancellationToken)' requires a receiver of type 'FluentValidation.IValidator<MiniLcm.Models.SemanticDomain>'
|
|
Dotnet build:
backend/FwLite/LcmCrdt/CrdtMiniLcmApi.cs#L160
'MiniLcmValidators' does not contain a definition for 'ValidateAndThrowAsync' and the best extension method overload 'DefaultValidatorExtensions.ValidateAndThrowAsync<SemanticDomain>(IValidator<SemanticDomain>, SemanticDomain, CancellationToken)' requires a receiver of type 'FluentValidation.IValidator<MiniLcm.Models.SemanticDomain>'
|
|
Dotnet build:
backend/FwLite/LcmCrdt/CrdtMiniLcmApi.cs#L144
'MiniLcmValidators' does not contain a definition for 'ValidateAndThrowAsync' and the best extension method overload 'DefaultValidatorExtensions.ValidateAndThrowAsync<SemanticDomain>(IValidator<SemanticDomain>, SemanticDomain, CancellationToken)' requires a receiver of type 'FluentValidation.IValidator<MiniLcm.Models.SemanticDomain>'
|
|
Dotnet build:
backend/FwLite/LcmCrdt/CrdtMiniLcmApi.cs#L160
'MiniLcmValidators' does not contain a definition for 'ValidateAndThrowAsync' and the best extension method overload 'DefaultValidatorExtensions.ValidateAndThrowAsync<SemanticDomain>(IValidator<SemanticDomain>, SemanticDomain, CancellationToken)' requires a receiver of type 'FluentValidation.IValidator<MiniLcm.Models.SemanticDomain>'
|
|
Dotnet build
Process completed with exit code 1.
|
|
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Dotnet build:
backend/FwLite/FwDataMiniLcmBridge/Api/FwDataMiniLcmApi.cs#L209
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.
|
|
Dotnet build:
backend/FwLite/FwDataMiniLcmBridge/LcmUtils/LcmThreadedProgress.cs#L10
The event 'LcmThreadedProgress.Canceling' is never used
|
|
Dotnet build:
backend/FwLite/FwDataMiniLcmBridge/Api/UpdateProxy/UpdateSenseProxy.cs#L121
Observe the awaitable result of this method call by awaiting it, assigning to a variable, or passing it to another method (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD110.md)
|
|
Dotnet build:
backend/FwLite/LcmCrdt/CrdtProjectsService.cs#L25
The default value specified for parameter 'saveChangesOnDispose' will have no effect because it applies to a member that is used in contexts that do not allow optional arguments
|
|
Dotnet build:
backend/FwLite/LcmCrdt/CrdtMiniLcmApi.cs#L19
Parameter 'dbContext' is unread.
|
|
Dotnet build:
backend/FwLite/LcmCrdt/Changes/RemoveSemanticDomainChange.cs#L11
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.
|
|
Dotnet build:
backend/FwLite/LcmCrdt/RemoteSync/CrdtHttpSyncService.cs#L53
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.
|
|
Dotnet build:
backend/FwLite/LcmCrdt/Data/SetupCollationInterceptor.cs#L27
The variable 'e' is declared but never used
|
|
Dotnet build:
backend/FwLite/LcmCrdt/HistoryService.cs#L94
The result of the expression is always 'true' since a value of type 'Guid' is never equal to 'null' of type 'Guid?'
|
|
Dotnet build:
backend/FwLite/LcmCrdt/HistoryService.cs#L94
The result of the expression is always 'true' since a value of type 'Guid' is never equal to 'null' of type 'Guid?'
|
Loading