Skip to content
This repository has been archived by the owner on Jul 12, 2020. It is now read-only.

Customize the CosmosEntityName property to avoid data migration #126

Open
pollax opened this issue Feb 26, 2020 · 1 comment
Open

Customize the CosmosEntityName property to avoid data migration #126

pollax opened this issue Feb 26, 2020 · 1 comment

Comments

@pollax
Copy link

pollax commented Feb 26, 2020

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?

@pollax
Copy link
Author

pollax commented Mar 2, 2020

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant