Merge pull request #21 from Panxuc/dev #94
This run and associated checks have been archived and are scheduled for deletion.
Learn more about checks retention
Annotations
10 warnings
dotnet-build:
logic/GameClass/GameObj/Team.cs#L135
Non-nullable field 'birthPointList' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
|
dotnet-build:
logic/GameClass/GameObj/Team.cs#L135
Non-nullable field 'home' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
|
dotnet-build:
logic/GameClass/GameObj/Ship.cs#L171
Non-nullable property 'Armor' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
dotnet-build:
logic/GameClass/GameObj/Ship.cs#L171
Non-nullable property 'Shield' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
dotnet-build:
logic/GameClass/GameObj/Ship.cs#L171
Non-nullable property 'BulletNum' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
dotnet-build:
logic/GameClass/GameObj/Team.cs#L17
Field 'Team.birthPointList' is never assigned to, and will always have its default value null
|
dotnet-build:
logic/Client/MainPage.xaml.cs#L588
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
dotnet-build:
logic/Client/MainPage.xaml.cs#L374
The variable 'ex' is declared but never used
|
dotnet-build:
logic/Client/MainPage.xaml.cs#L597
The field 'MainPage.unit' is never used
|
dotnet-build:
logic/Client/MainPage.xaml.cs#L596
The field 'MainPage.playerID' is never used
|