Customize the CosmosEntityName property to avoid data migration

Open pollax opened this issue 5 years ago • 1 comments

In my scenario, I already have a "shared" collection. Cosmonaut wasn't around at that time so we built our own variant of this. This one's better. ;)

So, we would like to move from our custom thing to Cosmonaut. Our documents have a property called DbType and not CosmosEntityName. It would be fantastic if it was possible to customize the property name that Cosmonaut looks for when doing lookups.

Currently, if we want to start using Cosmonaut we would have to do a massive data migration to add/rename the DbType field to CosmosEntityName.

Is this something you might consider adding?

Feb 26 '20 21:02 pollax

I should probably add that it's of course super easy to fork this lib and change the name, but I have a hunch I'm not the only one in this situation.

Mar 02 '20 12:03 pollax