New update #2
Annotations
11 warnings
build
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/.
|
build:
FCommerce.Models/Product.cs#L12
Non-nullable property 'ProductName' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
build:
FCommerce.Models/Product.cs#L14
Non-nullable property 'Description' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
build:
FCommerce.Models/Product.cs#L23
Non-nullable property 'Category' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
build:
FCommerce.Models/Category.cs#L10
Non-nullable property 'Name' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
build:
FCommerce.DataAcsess/Repos/Implimentations/Repositoy.cs#L41
Possible null reference return.
|
build:
FCommerce.DataAcsess/Repos/Implimentations/Repositoy.cs#L46
Possible null reference return.
|
build:
FCommerce.Website/Controllers/CategorysController.cs#L39
The result of the expression is always 'false' since a value of type 'int' is never equal to 'null' of type 'int?'
|
build:
FCommerce.Website/Controllers/ProductsController.cs#L84
The result of the expression is always 'false' since a value of type 'int' is never equal to 'null' of type 'int?'
|
build:
FCommerce.Models/Product.cs#L12
Non-nullable property 'ProductName' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
build:
FCommerce.Models/Product.cs#L14
Non-nullable property 'Description' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|