Skip to content

New movement

New movement #184

Triggered via pull request April 16, 2024 22:00
Status Success
Total duration 55s
Artifacts

dotnet.yml

on: pull_request
buildProject
47s
buildProject
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
buildProject: src/Shared/Messages/NewEntity.cs#L11
Non-nullable property 'name' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
buildProject: src/Shared/Messages/NewEntity.cs#L119
Non-nullable property 'name' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
buildProject: src/Shared/Messages/Join.cs#L14
Non-nullable property 'name' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
buildProject: src/Server/Systems/SpiceGenerator.cs#L31
Dereference of a possibly null reference.
buildProject: src/Server/Systems/Network.cs#L26
Non-nullable field 'm_joinHandler' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
buildProject: src/Server/Systems/Network.cs#L26
Non-nullable field 'm_disconnectHandler' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
buildProject: src/Server/Systems/CollisionDetection.cs#L21
Non-nullable field 'm_removeEntity' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
buildProject: src/Server/Systems/CollisionDetection.cs#L21
Non-nullable field 'm_addEntity' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
buildProject: src/Server/Systems/CollisionDetection.cs#L21
Non-nullable field 'm_updateEntity' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
buildProject: src/Server/MessageQueueServer.cs#L194
Dereference of a possibly null reference.