Skip to content

fixed aspire.net

fixed aspire.net #19

Triggered via push December 6, 2024 17:28
Status Success
Total duration 8m 21s
Artifacts 1

gdbapi.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

13 warnings
build
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: src/BlazorGDB/BlazorGDB.Client/Pages/Financials/ChartOfAccounts3.razor#L138
The field 'ChartOfAccounts3.data' is never used
build: 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: 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: 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: 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: src/Services/Sales/SalesService.cs#L735
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
build: src/Services/Sales/SalesService.cs#L736
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
build: src/Services/Sales/SalesService.cs#L774
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
build: src/Services/Sales/SalesService.cs#L775
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
build: 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)
build: 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)
build: 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)

Artifacts

Produced during runtime
Name Size
.net-app
16.2 MB