Skip to content

docs: add warning about Cosmos dB incompatibility #13350

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Braggedtooth
Copy link
Contributor

Update the docs to warn about Cosmos dB incompatibility with payload,

add warning about Cosmos dB incompatibility
Copy link
Contributor

@DanRibbens DanRibbens left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This could really be improved by talking about the new importable compatibilityOptions.cosmosdb option that was added recently. By spreading that option object into the adapter, devs don't need to flip individual switches and can instead have all the recommended settings applied.

@Braggedtooth
Copy link
Contributor Author

This could really be improved by talking about the new importable compatibilityOptions.cosmosdb option that was added recently. By spreading that option object into the adapter, devs don't need to flip individual switches and can instead have all the recommended settings applied.

Sure, I’ll include this! Although I see it’s already mentioned here.
Do you think it would make more sense to add the warning there about Cosmos DB’s limitations, or just update the pr to mention the compatibilityOptions.cosmosdb import as the recommended setup or both?

Happy to adjust based on what you think works best.

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

Successfully merging this pull request may close these issues.

2 participants