Complex forms in miniLcm #194
Annotations
2 errors and 10 warnings
|
Dotnet test:
backend/FwLite/FwLiteProjectSync.Tests/UpdateDiffTests.cs#L23
Expected property previous.Components to be a collection with 1 item(s), but found an empty collection.
Expected property previous.ComplexForms to be a collection with 1 item(s), but found an empty collection.
Expected property previous.ComplexFormTypes to be a collection with 1 item(s), but found an empty collection.
Expected property previous.Variants to be
MiniLcm.Models.Variants
{
Id = {bc841668-9a95-6ef5-54c7-9f8cc04016e4},
{
Types = MiniLcm.Models.VariantType
{
Id = {888004f7-c77c-f3b8-668c-1432bfe4c5d6},
Name = {[MiniLcm.Models.WritingSystemId
{
Code = "ci"
}] = "Gardens", [MiniLcm.Models.WritingSystemId
{
Code = "ut"
}] = "Well", [MiniLcm.Models.WritingSystemId
{
Code = "kf"
}] = "holistic", [MiniLcm.Models.WritingSystemId
{
Code = "fe"
}] = "synthesize"
}
}
},
VariantsOf = MiniLcm.Models.ComplexFormComponent
{
{
ComplexFormEntryId = {53c220f8-053c-37c0-9024-eb2bc96bc3c1},
ComplexFormHeadword = "Sharable",
ComponentEntryId = {fc7705a2-70f0-83af-5239-a8e2a4154fe0},
ComponentHeadword = "Facilitator",
ComponentSenseId = {bbf61e81-f6bd-0e79-554f-c7d110793b46},
Id = {ad30088b-066d-0793-60d6-e081ef063a53}
}
}
}, but found <null>.
With configuration:
- Use declared types and members
- Compare enums by value
- Compare tuples by their properties
- Compare anonymous types by their properties
- Compare records by their members
- Include non-browsable members
- Exclude member Id
- Exclude member Senses
- Match member by name (or throw)
- Be strict about the order of items in byte arrays
- Without automatic conversion.
|
|
Dotnet test
Process completed with exit code 1.
|
|
Dotnet build:
backend/FwLite/MiniLcm/InMemoryApi.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/MiniLcm/InMemoryApi.cs#L184
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#L216
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#L235
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/FwDataMiniLcmBridge/Api/UpdateProxy/UpdateEntryProxy.cs#L38
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/CrdtMiniLcmApi.cs#L17
Parameter 'timeProvider' 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/Changes/CreateSemanticDomainChange.cs#L18
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.
|
Loading