platform.bible extension poc #155
Annotations
25 warnings
Publish OSX ARM:
backend/FwLite/FwLiteProjectSync/DryRunMiniLcmApi.cs#L29
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.WritingSystemType)2' is not covered.
|
Publish OSX ARM:
backend/FwLite/LocalWebApp/SyncService.cs#L16
Parameter 'factory' is unread.
|
Publish OSX ARM:
backend/FwLite/LocalWebApp/CrdtHttpSyncService.cs#L64
Parameter 'originDomain' is unread.
|
Publish OSX ARM:
backend/FwLite/LocalWebApp/Routes/HistoryRoutes.cs#L45
The result of the expression is always 'true' since a value of type 'Guid' is never equal to 'null' of type 'Guid?'
|
Publish OSX ARM:
backend/FwLite/LocalWebApp/Routes/HistoryRoutes.cs#L45
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/MiniLcm/InMemoryApi.cs#L177
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/MiniLcm/InMemoryApi.cs#L182
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/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.
|
Dotnet build:
backend/FwLite/MiniLcm/InMemoryApi.cs#L233
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/Api/FwDataMiniLcmApi.cs#L171
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/Api/FwDataMiniLcmApi.cs#L179
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/Api/FwDataMiniLcmApi.cs#L193
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/Api/FwDataMiniLcmApi.cs#L206
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/Api/FwDataMiniLcmApi.cs#L289
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
|
Publish OSX:
backend/FwLite/MiniLcm/InMemoryApi.cs#L177
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.
|
Publish OSX:
backend/FwLite/MiniLcm/InMemoryApi.cs#L182
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.
|
Publish OSX:
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.
|
Publish OSX:
backend/FwLite/MiniLcm/InMemoryApi.cs#L233
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.
|
Publish OSX:
backend/FwLite/FwDataMiniLcmBridge/Api/FwDataMiniLcmApi.cs#L171
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.
|
Publish OSX:
backend/FwLite/FwDataMiniLcmBridge/Api/FwDataMiniLcmApi.cs#L179
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.
|
Publish OSX:
backend/FwLite/FwDataMiniLcmBridge/Api/FwDataMiniLcmApi.cs#L193
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.
|
Publish OSX:
backend/FwLite/FwDataMiniLcmBridge/Api/FwDataMiniLcmApi.cs#L206
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.
|
Publish OSX:
backend/FwLite/FwDataMiniLcmBridge/Api/FwDataMiniLcmApi.cs#L289
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.
|
Publish OSX:
backend/FwLite/FwDataMiniLcmBridge/LcmUtils/LcmThreadedProgress.cs#L10
The event 'LcmThreadedProgress.Canceling' is never used
|
Loading