upgrade packages #60
SitholeWBAnnotations
11 warnings
|
build
Node.js 12 actions are deprecated. Please update the following actions to use Node.js 16: actions/checkout@v2, actions/setup-dotnet@v1. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/.
|
|
build:
Examples/WebApi/DTOs/CountryDto.cs#L6
Non-nullable property 'Name' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
build:
Examples/WebApi/Entities/Country.cs#L6
Non-nullable property 'Name' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
build:
Examples/WebApi/Models/UpdateCountryModel.cs#L5
Non-nullable property 'Name' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
build:
Examples/WebApi/Models/AddCountryModel.cs#L5
Non-nullable property 'Name' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
build:
Examples/BlazorApp.SQLite/DTOs/CountryDto.cs#L6
Non-nullable property 'Name' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
build:
Examples/BlazorApp.SQLite/Entities/Country.cs#L6
Non-nullable property 'Name' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
build:
Examples/BlazorApp.SQLite/Models/UpdateCountryModel.cs#L5
Non-nullable property 'Name' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
build:
Examples/BlazorApp.SQLite/Models/AddCountryModel.cs#L5
Non-nullable property 'Name' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
build:
Examples/BlazorApp.SQLite/Pages/Countries.razor#L92
Possible null reference argument for parameter 'country' in 'Task<Country> CountryService.AddCountryAsync(AddCountryModel country)'.
|
|
build:
Pagination.EntityFrameworkCore.Extensions.Tests/UnitTests.cs#L39
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|