fix db hash in recreate issue #45
Annotations
11 warnings
|
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-dotnet@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
Build:
examples/ExampleWeb/Program.cs#L51
Possible null reference argument for parameter 'entity' in 'EntityEntry<User> DbSet<User>.Add(User entity)'.
|
|
Build:
src/MccSoft.IntegreSql.EF/DatabaseInitialization/ContextHelper.cs#L16
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Build:
examples/ExampleWeb/Database/ExampleDbContext.cs#L9
Non-nullable property 'Users' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Build:
src/MccSoft.IntegreSql.EF/DatabaseInitialization/DatabaseSeedingOptions.cs#L9
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Build:
src/MccSoft.IntegreSql.EF/DatabaseInitialization/DatabaseSeedingOptions.cs#L10
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Build:
src/MccSoft.IntegreSql.EF/SqliteDatabaseInitializer.cs#L58
The variable 'e' is declared but never used
|
|
Build:
examples/ExampleWeb/Database/User.cs#L6
Non-nullable property 'Name' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Build:
tests/ExampleWeb.UnitTests/NoMigrationTests.cs#L15
Non-nullable property 'Title' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Build:
tests/ExampleWeb.UnitTests/NoMigrationTests.cs#L22
Non-nullable property 'Entity1' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
|
|
Build:
tests/ExampleWeb.UnitTests/SeedingFunctionThrowsTests.cs#L30
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.
|
Loading