Use correct audience for invitation-email and make API unambiguous (#… #44
Annotations
1 error and 32 warnings
|
Integration tests
Process completed with exit code 1.
|
|
Publish unit test results
Running this action via 'uses: EnricoMi/publish-unit-test-result-action/composite@v2 is deprecated! For details, see: https://github.com/EnricoMi/publish-unit-test-result-action/tree/v2#running-as-a-composite-action
|
|
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/.
|
|
Dotnet build:
backend/FixFwData/Program.cs#L1
The variable 'doNothing' is assigned but its value is never used
|
|
Dotnet build:
backend/LexCore/Entities/ProjectUsers.cs#L8
Non-nullable property 'User' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Dotnet build:
backend/LexCore/Entities/ProjectUsers.cs#L9
Non-nullable property 'Project' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Dotnet build:
backend/LexCore/Entities/Project.cs#L82
Non-nullable property 'Node' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Dotnet build:
backend/LexCore/Entities/Project.cs#L84
Non-nullable property 'Date' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Dotnet build:
backend/LexCore/Entities/Project.cs#L85
Non-nullable property 'Desc' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Dotnet build:
backend/LexCore/Entities/Project.cs#L87
Non-nullable property 'Branch' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Dotnet build:
backend/LexCore/Entities/Project.cs#L91
Non-nullable property 'Tags' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Dotnet build:
backend/LexCore/Entities/Project.cs#L92
Non-nullable property 'User' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Dotnet build:
backend/LexCore/Entities/Project.cs#L93
Non-nullable property 'Phase' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Build for tests:
backend/Testing/SyncReverseProxy/SendReceiveServiceTests.cs#L160
Dereference of a possibly null reference.
|
|
Build for tests:
backend/Testing/SyncReverseProxy/SendReceiveServiceTests.cs#L160
Dereference of a possibly null reference.
|
|
Build for tests:
backend/Testing/SyncReverseProxy/SendReceiveServiceTests.cs#L160
Dereference of a possibly null reference.
|
|
Build for tests:
backend/Testing/SyncReverseProxy/SendReceiveServiceTests.cs#L178
Dereference of a possibly null reference.
|
|
Build for tests:
backend/Testing/SyncReverseProxy/SendReceiveServiceTests.cs#L178
Dereference of a possibly null reference.
|
|
Build for tests:
backend/Testing/SyncReverseProxy/SendReceiveServiceTests.cs#L178
Dereference of a possibly null reference.
|
|
Build for tests:
backend/Testing/LexCore/LexAuthUserTests.cs#L55
Possible null reference argument for parameter 'value' in 'Claim.Claim(string type, string value)'.
|
|
Build for tests:
backend/Testing/LexCore/LexAuthUserTests.cs#L182
Dereference of a possibly null reference.
|
|
Build for tests:
backend/Testing/LexCore/Services/HgServiceTests.cs#L86
Avoid "async void" methods, because any exceptions not handled by the method will crash the process (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD100.md)
|
|
Build for tests:
backend/Testing/SyncReverseProxy/SendReceiveServiceTests.cs#L160
Dereference of a possibly null reference.
|
|
Integration tests
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
|
|
Integration tests:
backend/LexBoxApi/Auth/Attributes/LexboxAuthAttribute.cs#L15
Nullability of reference types in type of parameter 'value' of 'void LexboxAuthAttribute.Policy.set' doesn't match implicitly implemented member 'void IAuthorizeData.Policy.set' (possibly because of nullability attributes).
|
|
Integration tests:
backend/LexBoxApi/Services/EmailService.cs#L102
Cannot convert null literal to non-nullable reference type.
|
|
Integration tests:
backend/LexBoxApi/Services/UserService.cs#L7
Parameter 'lexAuthService' is unread.
|
|
Integration tests:
backend/LexBoxApi/Auth/LoggedInContext.cs#L24
Possible null reference argument for parameter 'activity' in 'void ActivityExtensions.RecordException(Activity activity, Exception? ex)'.
|
|
Integration tests:
backend/LexBoxApi/GraphQL/UserMutations.cs#L46
Possible null reference assignment.
|
|
Integration tests:
backend/LexBoxApi/GraphQL/UserMutations.cs#L114
Possible null reference argument for parameter 'newAdminEmail' in 'Task EmailService.SendNewAdminEmail(IAsyncEnumerable<User> admins, string newAdminName, string newAdminEmail)'.
|
|
Integration tests:
backend/LexBoxApi/Jobs/CleanupResetBackupJob.cs#L7
Parameter 'hgService' is unread.
|
|
Integration tests:
backend/LexBoxApi/Controllers/LoginController.cs#L32
Parameter 'projectService' is unread.
|
|
Integration tests:
backend/LexBoxApi/Auth/JwtTicketDataFormat.cs#L122
'JwtBearerOptions.SecurityTokenValidators' is obsolete: 'SecurityTokenValidators is no longer used by default. Use TokenHandlers instead. To continue using SecurityTokenValidators, set UseSecurityTokenValidators to true. See https://aka.ms/aspnetcore8/security-token-changes'
|
Loading