Migration failed to add a field to the CatalogItem entity in CatalogContext of Catalog.API

[anjoy8]

1.First, I added a String field: Tests

public string Tests { get; set; }

2.Then, to perform the migration:

 add - migration AddTests - c CatalogContext - o Infrastructure/CatalogMigrations

3.Finally, execute the project(or update-database) and report an error

---

After Debugging the source code, I found that the last migration record was not synchronized into the model snapshot.

This submission record has been modified.
(45ed8a6)
But the snapshot file has not changed.
（https://github.com/dotnet-architecture/eShopOnContainers/blob/dev/src/Services/Catalog/Catalog.API/Infrastructure/CatalogMigrations/CatalogContextModelSnapshot.cs）

Causes new fields to be added to conflict.

[anjoy8]

The project only needs to modify the Model snapshot,

and I can submit PR if necessary.

[sughosneo]

Hey @anjoy8, good to hear back from you again. :)

I quickly tried to run a migration by adding one Test string field and I was able to update the CatalogContextModelSnapshot class with new migration command.

dotnet ef migrations add AddTests -c CatalogContext -o Infrastructure/CatalogMigrations

But yes, there is some issues with PictureUri and now instead of that we have been using PictureFileName for the Catalog item. You may want to look into issue #1350 and propose the necessary changes.

Thank you

[anjoy8]

Hi, @sughosneo nice to hear from you again.

Regarding my issue, only need to modify the model snapshot.

On the issue of the (#1350), I have found the problem, do I need to submit a PR?

Just change pictureFileName to lowercase.

pictureFileName -> picturefilename

need I need to submit a PR?

[sughosneo]

Hi, @sughosneo nice to hear from you again.

Regarding my issue, only need to modify the model snapshot.

On the issue of the (#1350), I have found the problem, do I need to submit a PR?

Just change pictureFileName to lowercase.

pictureFileName -> picturefilename

need I need to submit a PR?

Yes, you are correct. I thought of pointing that one as well. Yes, you could submit two separate PRs with the respective changes.

Thank you.

[anjoy8]

Hi, I had intended to submit two PRs, but eventually merge together, #1520
I wonder if this meets your requirements.

In addition, there may still be some problems about Seed data, and I will further study it.