azure-webapps-dotnet-core.yml
on: push
build
35s
deploy
17s
Annotations
11 warnings
|
build:
whateverAPI/Endpoints/UserEndpoints.cs#L49
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.
|
|
build:
whateverAPI/Services/RoleService.cs#L111
Dereference of a possibly null reference.
|
|
build:
whateverAPI/Entities/User.cs#L79
Dereference of a possibly null reference.
|
|
build:
whateverAPI/Services/MicrosoftAuthService.cs#L140
Unreachable code detected
|
|
build:
whateverAPI/Entities/Role.cs#L13
Non-nullable property 'Name' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
|
build:
whateverAPI/Endpoints/AuthEndpoints.cs#L80
Unreachable code detected
|
|
build:
whateverAPI/Endpoints/AuthEndpoints.cs#L156
Unreachable code detected
|
|
build:
whateverAPI/Endpoints/AuthEndpoints.cs#L186
Unreachable code detected
|
|
build:
whateverAPI/Endpoints/AuthEndpoints.cs#L49
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.
|
|
build:
whateverAPI/Endpoints/AuthEndpoints.cs#L127
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.
|
|
build
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.
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
.net-app
Expired
|
8.67 MB |
sha256:ceb7fafab3af31a19f856134e463d03553713267a147c9a008b1ed610264ee02
|
|