Fix some redaction issues #144
Annotations
11 warnings
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-dotnet@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
ReplayBrowser/Data/UsernameResponse.cs#L5
Non-nullable property 'userName' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
ReplayBrowser/Data/UsernameResponse.cs#L7
Non-nullable property 'userId' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
ReplayBrowser/Pages/ViewReplay.razor#L26
Non-nullable property 'Id' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
ReplayBrowser/Controllers/AccountController.cs#L48
Dereference of a possibly null reference.
|
ReplayBrowser/Controllers/AccountController.cs#L79
Dereference of a possibly null reference.
|
ReplayBrowser/Controllers/AccountController.cs#L105
Cannot convert null literal to non-nullable reference type.
|
ReplayBrowser/Helpers/Ss14ApiHelper.cs#L27
Converting null literal or possible null value to non-nullable type.
|
ReplayBrowser/Helpers/Ss14ApiHelper.cs#L34
Dereference of a possibly null reference.
|
ReplayBrowser/Data/AccountHistoryResponse.cs#L7
Non-nullable property 'History' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
ReplayBrowser/Data/PlayerData.cs#L10
Non-nullable property 'Username' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
This job succeeded
Loading