Add purchase datagrid and fetch purchases from db (#44) #29
deploy-dev.yml
on: push
dev-deploy
/
...
/
Build and test Webapp
1m 22s
dev-deploy
/
...
/
Build ARM template
24s
dev-deploy
/
Azure Deployment
2m 35s
Annotations
17 warnings
dev-deploy / Build codebase / Build webapp / Build and test Webapp
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
dev-deploy / Build codebase / Build webapp / Build and test Webapp:
Shifty.App/Shared/MainLayout.razor#L47
'Palette' is obsolete: 'This property will be abstract in a future update. Use PaletteLight, PaletteDark or your own implementation.'
|
dev-deploy / Build codebase / Build webapp / Build and test Webapp:
Shifty.App/Components/Voucher.razor#L134
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.
|
dev-deploy / Build codebase / Build webapp / Build and test Webapp:
Shifty.App/Components/ProductManager.razor#L150
Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.
|
dev-deploy / Build codebase / Build webapp / Build and test Webapp:
Shifty.App/Components/Refunds.razor#L64
The field 'Refunds._loading' is assigned but its value is never used
|
dev-deploy / Build codebase / Build webapp / Build and test Webapp:
Shifty.App/Shared/MainLayout.razor#L47
'Palette' is obsolete: 'This property will be abstract in a future update. Use PaletteLight, PaletteDark or your own implementation.'
|
dev-deploy / Build codebase / Build webapp / Build and test Webapp:
Shifty.App/Components/Voucher.razor#L134
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.
|
dev-deploy / Build codebase / Build webapp / Build and test Webapp:
Shifty.App/Components/ProductManager.razor#L150
Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.
|
dev-deploy / Build codebase / Build webapp / Build and test Webapp:
Shifty.App/Components/Refunds.razor#L64
The field 'Refunds._loading' is assigned but its value is never used
|
dev-deploy / Build codebase / Build webapp / Build and test Webapp
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
|
dev-deploy / Build codebase / Build webapp / Build and test Webapp:
Shifty.App/Shared/MainLayout.razor#L47
'Palette' is obsolete: 'This property will be abstract in a future update. Use PaletteLight, PaletteDark or your own implementation.'
|
dev-deploy / Build codebase / Build webapp / Build and test Webapp:
Shifty.App/Components/Voucher.razor#L134
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.
|
dev-deploy / Build codebase / Build webapp / Build and test Webapp:
Shifty.App/Components/ProductManager.razor#L150
Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.
|
dev-deploy / Build codebase / Build webapp / Build and test Webapp:
Shifty.App/Components/Refunds.razor#L64
The field 'Refunds._loading' is assigned but its value is never used
|
dev-deploy / Build codebase / Build infrastructure / Build ARM template
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
dev-deploy / Azure Deployment
The following actions use a deprecated Node.js version and will be forced to run on node20: azure/login@v1, actions/download-artifact@v3, azure/arm-deploy@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "arm", "shifty".
Please update your workflow to use v4 of the artifact actions.
Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
arm
Expired
|
7.11 KB |
|
shifty
Expired
|
38.2 MB |
|