We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The Azure portal, MS docs and V3 SDK all use Container in preference to Collection consistently.
Based on this, I feel all Cosmos related APIs should reflect that - this would affect things with Collection in the name.
Collection
I'm also thinking that the EQUINOX_COSMOS_COLLECTION env var used by eqx and dotenet-templates should also be changed at this time.
EQUINOX_COSMOS_COLLECTION
eqx
See changes queued in #144
The text was updated successfully, but these errors were encountered:
Resolved in #149
Sorry, something went wrong.
No branches or pull requests
The Azure portal, MS docs and V3 SDK all use Container in preference to Collection consistently.
Based on this, I feel all Cosmos related APIs should reflect that - this would affect things with
Collection
in the name.I'm also thinking that the
EQUINOX_COSMOS_COLLECTION
env var used byeqx
and dotenet-templates should also be changed at this time.See changes queued in #144
The text was updated successfully, but these errors were encountered: