fix:微調 #63
build-and-deploy.yml
on: push
Build, Test and Publish Artifact
43s
Annotations
10 warnings
Build, Test and Publish Artifact:
Domain/Player.cs#L15
Non-nullable field 'chess' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
|
Build, Test and Publish Artifact:
Domain/Player.cs#L15
Non-nullable field 'auction' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
|
Build, Test and Publish Artifact:
Domain/Player.cs#L15
Non-nullable property 'Monopoly' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
Build, Test and Publish Artifact:
Domain/Auction.cs#L26
Dereference of a possibly null reference.
|
Build, Test and Publish Artifact:
Domain/Monopoly.cs#L233
Dereference of a possibly null reference.
|
Build, Test and Publish Artifact:
Client/Pages/Game.razor.cs#L42
Dereference of a possibly null reference.
|
Build, Test and Publish Artifact:
Client/Pages/Game.razor.cs#L9
Non-nullable property 'Id' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
Build, Test and Publish Artifact:
Application/Usecases/CreateGameUsecase.cs#L16
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, Test and Publish Artifact:
Test/ServerTests/AcceptanceTests/RollDiceTest.cs#L141
Possible null reference argument for parameter 'Land' in 'LandContract.LandContract(Player? Owner, Land Land)'.
|
Build, Test and Publish Artifact:
Test/ServerTests/Utils.cs#L45
Non-nullable property 'Game' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|