Minilcm diff API #328
fw-lite.yaml
on: pull_request
Build FW Lite and run tests
3m 20s
Publish FW Lite app for Mac
0s
Publish FW Lite app for Linux
0s
Publish FW Lite app for Windows
0s
Create Release
0s
Annotations
3 errors and 10 warnings
Build FW Lite and run tests:
backend/FwLite/LocalWebApp/Routes/HistoryRoutes.cs#L35
'DataModel' does not contain a definition for 'GetEntitySnapshotAtTime' and no accessible extension method 'GetEntitySnapshotAtTime' accepting a first argument of type 'DataModel' could be found (are you missing a using directive or an assembly reference?)
|
Build FW Lite and run tests:
backend/FwLite/LocalWebApp/Routes/HistoryRoutes.cs#L35
'DataModel' does not contain a definition for 'GetEntitySnapshotAtTime' and no accessible extension method 'GetEntitySnapshotAtTime' accepting a first argument of type 'DataModel' could be found (are you missing a using directive or an assembly reference?)
|
Build FW Lite and run tests
Process completed with exit code 1.
|
Build FW Lite and run tests:
backend/FwLite/MiniLcm/InMemoryApi.cs#L214
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 FW Lite and run tests:
backend/FwLite/MiniLcm/InMemoryApi.cs#L219
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 FW Lite and run tests:
backend/FwLite/MiniLcm/InMemoryApi.cs#L251
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 FW Lite and run tests:
backend/FwLite/MiniLcm/InMemoryApi.cs#L270
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 FW Lite and run tests:
backend/FwLite/FwDataMiniLcmBridge/LcmUtils/LcmThreadedProgress.cs#L10
The event 'LcmThreadedProgress.Canceling' is never used
|
Build FW Lite and run tests:
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)
|
Build FW Lite and run tests:
backend/FwLite/FwDataMiniLcmBridge/Api/UpdateProxy/UpdateEntryProxy.cs#L53
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)
|
Build FW Lite and run tests:
backend/FwLite/LcmCrdt/CrdtMiniLcmApi.cs#L15
Parameter 'dbContext' is unread.
|
Build FW Lite and run tests:
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.
|
Build FW Lite and run tests:
backend/FwLite/FwLiteProjectSync/DryRunMiniLcmApi.cs#L30
The switch expression does not handle some values of its input type (it is not exhaustive) involving an unnamed enum value. For example, the pattern '(MiniLcm.Models.WritingSystemType)2' is not covered.
|