Update dependency FluentValidation to v11.9.2 · DFE-Digital/record-concerns-support-trusts@2d22b77

Triggered via pull request June 28, 2024 15:40

synchronize #1228

Status Success

Total duration 4m 20s

Artifacts –

continuous-integration-dotnet.yml

on: pull_request

10 warnings

build-test: ConcernsCaseWork/ConcernsCaseWork.UserContext/ClientUserInfoService.cs#L14

Non-nullable property 'UserInfo' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

build-test: ConcernsCaseWork/ConcernsCaseWork.UserContext/UserInfo.cs#L41

Possible null reference return.

build-test: ConcernsCaseWork/ConcernsCaseWork.UserContext/UserInfo.cs#L8

Non-nullable property 'Name' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

build-test: ConcernsCaseWork/ConcernsCaseWork.UserContext/UserInfo.cs#L9

Non-nullable property 'Roles' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.

build-test: ConcernsCaseWork/ConcernsCaseWork.Utils/Extensions/DateExtension.cs#L24

Possible null reference return.

build-test: ConcernsCaseWork/ConcernsCaseWork.Utils/Extensions/EnumExtensions.cs#L11

Converting null literal or possible null value to non-nullable type.

build-test: ConcernsCaseWork/ConcernsCaseWork.Utils/Extensions/EnumExtensions.cs#L15

Possible null reference return.

build-test: ConcernsCaseWork/ConcernsCaseWork.Utils/Extensions/StringExtension.cs#L40

Possible null reference assignment.

build-test: ConcernsCaseWork/ConcernsCaseWork.Utils/Extensions/StringExtension.cs#L79

Possible null reference return.

build-test: ConcernsCaseWork/ConcernsCaseWork.API.Contracts/Case/ActiveCaseSummaryResponse.cs#L24

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.