chore: remove deploy.yml #3
Annotations
11 warnings
|
Build with dotnet:
AdminHubApi/Program.cs#L86
Possible null reference argument for parameter 's' in 'byte[] Encoding.GetBytes(string s)'.
|
|
Build with dotnet:
AdminHubApi/Models/AppUserProject.cs#L8
Non-nullable property 'AppUserId' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
|
Build with dotnet:
AdminHubApi/Models/AppUserProject.cs#L10
Non-nullable property 'AppUser' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
|
Build with dotnet:
AdminHubApi/Models/AppUserProject.cs#L11
Non-nullable property 'Project' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
|
Build with dotnet:
AdminHubApi/Mappers/ProjectCommentMapper.cs#L16
Possible null reference assignment.
|
|
Build with dotnet:
AdminHubApi/Extensions/ClaimsExtensions.cs#L9
Dereference of a possibly null reference.
|
|
Build with dotnet:
AdminHubApi/Models/ProjectComment.cs#L14
Non-nullable property 'AppUserId' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
|
Build with dotnet:
AdminHubApi/Models/ProjectComment.cs#L15
Non-nullable property 'AppUser' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
|
Build with dotnet:
AdminHubApi/Dtos/Project/ProjectDto.cs#L11
Non-nullable property 'Comments' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
|
Build with dotnet:
AdminHubApi/Service/TokenService.cs#L18
Possible null reference argument for parameter 's' in 'byte[] Encoding.GetBytes(string s)'.
|
|
dotnet publish
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.
|
Loading