fixed aspire.net #19
Annotations
13 warnings
Build with dotnet
Detected Razor language version downgrade. This is typically caused by a reference to the Microsoft.AspNetCore.Razor.Design package. Consider removing this package reference.
|
Build with dotnet:
src/BlazorGDB/BlazorGDB.Client/Pages/Financials/ChartOfAccounts3.razor#L138
The field 'ChartOfAccounts3.data' is never used
|
Build with dotnet:
src/BlazorGDB/BlazorGDB.Client/Pages/Financials/ChartOfAccounts3.razor#L135
Field 'ChartOfAccounts3.shouldRender' is never assigned to, and will always have its default value false
|
Build with dotnet:
src/BlazorGDB/BlazorGDB.Client/Pages/Financials/ChartOfAccounts.razor#L136
Field 'ChartOfAccounts.shouldRender' is never assigned to, and will always have its default value false
|
Build with dotnet:
src/BlazorGDB/BlazorGDB.Client/Pages/Financials/ChartOfAccounts3.razor#L134
Field 'ChartOfAccounts3.getError' is never assigned to, and will always have its default value false
|
Build with dotnet:
src/Core/Domain/Error/Result.cs#L8
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
Build with dotnet:
src/Services/Sales/SalesService.cs#L735
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
Build with dotnet:
src/Services/Sales/SalesService.cs#L736
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
Build with dotnet:
src/Services/Sales/SalesService.cs#L774
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
Build with dotnet:
src/Services/Sales/SalesService.cs#L775
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
dotnet publish:
src/Api/Controllers/TaxController.cs#L225
Route '{id:int}' conflicts with another action route. An HTTP request that matches multiple routes results in an ambiguous match error. Fix the conflict by changing the route's pattern, HTTP method, or route constraints. (https://aka.ms/aspnet/analyzers)
|
dotnet publish:
src/Api/Controllers/TaxController.cs#L239
Route '{id:int}' conflicts with another action route. An HTTP request that matches multiple routes results in an ambiguous match error. Fix the conflict by changing the route's pattern, HTTP method, or route constraints. (https://aka.ms/aspnet/analyzers)
|
dotnet publish:
src/Api/Controllers/TaxController.cs#L253
Route '{id:int}' conflicts with another action route. An HTTP request that matches multiple routes results in an ambiguous match error. Fix the conflict by changing the route's pattern, HTTP method, or route constraints. (https://aka.ms/aspnet/analyzers)
|
Loading