Strange behaver in migration

[T-Alkathiri]

Hi All,
I am trying to add my own table to the project with the following steps :
1- I created a class named Item as shown
public class Item : AuditableEntity, IAggregateRoot
{
public int ItemId { get; set; }
public string? ItemCode { get; set; }
public string? ItemName { get; set; }
}
2- I added the dbset to the ApplicationDbContext
public DbSet Items => Set();
3- I added the following steps to the Catalog.cs
public class ItemConfig : IEntityTypeConfiguration
{
public void Configure(EntityTypeBuilder builder)
{
builder.IsMultiTenant();

            builder
                .HasKey(b => b.ItemId);
            builder
                .Property(b => b.ItemId)
                .ValueGeneratedOnAdd();
    
        }
    }

4- I added migration to the ApplicationDbContext
Add-Migration ItemAdded -context ApplicationDbContext
And every things goes good and smoothly, But in the generated migration I found some thing strange when created :
protected override void Up(MigrationBuilder migrationBuilder)
{
**migrationBuilder.DropColumn(
name: "Description",
schema: "Identity",
table: "RoleClaims");

                  migrationBuilder.DropColumn(
                      name: "Group",
                      schema: "Identity",
                      table: "RoleClaims");
      
                  migrationBuilder.DropColumn(
                      name: "LastModifiedBy",
                      schema: "Identity",
                      table: "RoleClaims");
      
                  migrationBuilder.DropColumn(
                      name: "LastModifiedOn",
                      schema: "Identity",
                      table: "RoleClaims");**
      
                  migrationBuilder.CreateTable(
                      name: "Items",
                      schema: "Catalog",
                      columns: table => new
                      {
                          ItemId = table.Column<int>(type: "int", nullable: false)
                              .Annotation("SqlServer:Identity", "1, 1"),
                          ItemCode = table.Column<string>(type: "nvarchar(max)", nullable: true),
                          ItemName = table.Column<string>(type: "nvarchar(max)", nullable: true),
                          TenantId = table.Column<string>(type: "nvarchar(64)", maxLength: 64, nullable: false),
                          Id = table.Column<Guid>(type: "uniqueidentifier", nullable: false),
                          CreatedBy = table.Column<Guid>(type: "uniqueidentifier", nullable: false),
                          CreatedOn = table.Column<DateTime>(type: "datetime2", nullable: false),
                          LastModifiedBy = table.Column<Guid>(type: "uniqueidentifier", nullable: false),
                          LastModifiedOn = table.Column<DateTime>(type: "datetime2", nullable: true),
                          DeletedOn = table.Column<DateTime>(type: "datetime2", nullable: true),
                          DeletedBy = table.Column<Guid>(type: "uniqueidentifier", nullable: true)
                      },
                      constraints: table =>
                      {
                          table.PrimaryKey("PK_Items", x => x.ItemId);
                      });

it drops the Description,Group,LastModifiedBy and LastModifiedOn columns from the RoleClaims table and then create my Items table.
Knowing that I did not touch the Identities tables, and I have clone the updated FSH.WebApi as date of 17/05/2022
Is this normal or did I messed something, Please can some one help in this issue.
Thanks a lot for all community members.

[fretje]

It's not you... these are some of the latest changes that have been done in the code, and apparently the initial migrations haven't been re-created yet to accommodate those changes.

I just created this issue (#674) to make this automatic and part of the build process (hopefully).

[T-Alkathiri]

Thank you so much.

[T-Alkathiri]

In the mean time what should I do, Do I have to remove the drops column from the migration or leave it and then fixed when the issue solved.
Thank you very much.

[fretje]

No you can leave them there... Those columns aren't used anymore... Recreating the initial migrations would result in the same dB schema as you have now.

[T-Alkathiri]

Now it is clear.
Thank you very much