The using directive for 'BlotzTask.Models' appeared previously in this namespace

Non-nullable property 'TaskItems' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.

Possible null reference argument for parameter 'user' in 'Task<IdentityResult> UserManager<User>.AddClaimsAsync(User user, IEnumerable<Claim> claims)'.

Non-nullable property 'Title' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.

Non-nullable property 'Description' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.

Non-nullable property 'UserId' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.

Non-nullable property 'User' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.

The variable 'ex' is declared but never used

Possible null reference argument for parameter 'uriString' in 'Uri.Uri(string uriString)'.

Non-nullable property 'Title' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.

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.

The following actions uses node12 which is deprecated and will be forced to run on node16: Azure/get-keyvault-secrets@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: Azure/get-keyvault-secrets@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/