Implemented get all label endpoint (#98) #25
Annotations
11 warnings
Build with dotnet:
blotztask-api/Program.cs#L53
Possible null reference argument for parameter 'uriString' in 'Uri.Uri(string uriString)'.
|
Build with dotnet:
blotztask-api/Services/TaskService.cs#L36
The variable 'ex' is declared but never used
|
Build with dotnet:
blotztask-api/Data/Entities/User.cs#L6
Non-nullable property 'TaskItems' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
Build with dotnet:
blotztask-api/Data/Entities/TaskItem.cs#L10
Non-nullable property 'Title' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
Build with dotnet:
blotztask-api/Data/Entities/TaskItem.cs#L11
Non-nullable property 'Description' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
Build with dotnet:
blotztask-api/Models/TaskItemDTO.cs#L6
Non-nullable property 'Title' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
Build with dotnet:
blotztask-api/Models/TaskItemDTO.cs#L7
Non-nullable property 'Description' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
Build with dotnet:
blotztask-api/Services/LabelService.cs#L36
The variable 'ex' is declared but never used
|
Build with dotnet:
blotztask-api/Models/AddTaskItemDTO.cs#L10
Non-nullable property 'Title' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
Build with dotnet:
blotztask-api/Models/AddTaskItemDTO.cs#L11
Non-nullable property 'Description' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
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