Skip to content

1.7 fixes

1.7 fixes #23

Triggered via pull request June 3, 2024 16:07
Status Success
Total duration 34s
Artifacts

unit-tests.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

11 warnings
build
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/.
build: Basalt/Common/Utils/ResourceCache.cs#L92
Possible null reference assignment.
build: Basalt/Common/Utils/ResourceCache.cs#L97
Possible null reference assignment.
build: Basalt/Common/Utils/ResourceCache.cs#L116
Converting null literal or possible null value to non-nullable type.
build: Basalt/Common/Utils/ResourceCache.cs#L117
Possible null reference argument for parameter 'value' in 'void Dictionary<string, object>.Add(string key, object value)'.
build: Basalt/Common/Utils/ResourceCache.cs#L9
Non-nullable field 'instance' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
build: Basalt/Common/Time.cs#L29
Non-nullable field 'instance' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.
build: Basalt/Common/Physics/Octree.cs#L65
Converting null literal or possible null value to non-nullable type.
build: Basalt/Common/Events/EventBus.cs#L33
Cannot convert null literal to non-nullable reference type.
build: Basalt/Common/Events/EventBus.cs#L49
Possible null reference assignment.
build: Basalt/Common/Components/Rigidbody.cs#L41
Non-nullable field 'physicsEngine' must contain a non-null value when exiting constructor. Consider declaring the field as nullable.