Store user's yay/boo/meh faces #1878
Annotations
22 warnings
|
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v3, actions/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Publish for Windows x64:
Refresh.GameServer/Types/Challenges/SerializedGameChallengeList.cs#L70
Non-nullable property 'LamsDescriptionId' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Publish for Windows x64:
Refresh.GameServer/Types/Challenges/SerializedGameChallengeList.cs#L76
Non-nullable property 'LamsTitleId' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Publish for Windows x64:
Refresh.GameServer/Types/Challenges/SerializedGameChallengeList.cs#L91
Non-nullable property 'Content' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Publish for Windows x64:
Refresh.GameServer/Types/Challenges/SerializedGameChallengeList.cs#L97
Non-nullable property 'ContentName' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Publish for Windows x64:
Refresh.GameServer/Types/Challenges/SerializedGameChallengeList.cs#L100
Non-nullable property 'PlanetUser' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Publish for Windows x64:
Refresh.GameServer/Types/Challenges/SerializedGameChallengeList.cs#L43
Non-nullable property 'Challenges' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Publish for Windows x64
Possible null reference assignment.
|
|
Publish for Windows x64
Possible null reference assignment.
|
|
Publish for Windows x64
Possible null reference assignment.
|
|
Publish for Windows x64
Possible null reference assignment.
|
|
Publish for Linux x64:
Refresh.GameServer/Types/Challenges/SerializedGameChallengeList.cs#L70
Non-nullable property 'LamsDescriptionId' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Publish for Linux x64:
Refresh.GameServer/Types/Challenges/SerializedGameChallengeList.cs#L76
Non-nullable property 'LamsTitleId' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Publish for Linux x64:
Refresh.GameServer/Types/Challenges/SerializedGameChallengeList.cs#L91
Non-nullable property 'Content' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Publish for Linux x64:
Refresh.GameServer/Types/Challenges/SerializedGameChallengeList.cs#L97
Non-nullable property 'ContentName' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Publish for Linux x64:
Refresh.GameServer/Types/Challenges/SerializedGameChallengeList.cs#L100
Non-nullable property 'PlanetUser' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Publish for Linux x64:
Refresh.GameServer/Types/Challenges/SerializedGameChallengeList.cs#L43
Non-nullable property 'Challenges' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Publish for Linux x64:
Refresh.GameServer/Types/Assets/GameAssetType.cs#L480
The switch expression does not handle all possible values of its input type (it is not exhaustive). For example, the pattern 'Refresh.GameServer.Types.Assets.GameAssetType.Unknown' is not covered.
|
|
Publish for Linux x64
Possible null reference assignment.
|
|
Publish for Linux x64
Possible null reference assignment.
|
|
Publish for Linux x64
Possible null reference assignment.
|
|
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "Refresh for Linux x64", "Refresh for Windows x64".
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/
|
Loading