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
At the moment is it confusing having different writings in collectionNames and FieldNames.
My Suggestion is to use snake case in general and to prefix every system field with mc_ .
Example:
mc_roles fields: mc_name mc_is_admin mc_collection_grants or mc_users: mc_user_id mc_password mc_api_key mc_roles
If someone decides to extend mc_users with more fields, it is easy to distinguish between mongocamp system fields and additional fields.
Also every plugin made by mongocamp should use this name convention. So it will be easy for plugins to protect system fields in future.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
At the moment is it confusing having different writings in collectionNames and FieldNames.
My Suggestion is to use snake case in general and to prefix every system field with mc_ .
Example:
If someone decides to extend mc_users with more fields, it is easy to distinguish between mongocamp system fields and additional fields.
Also every plugin made by mongocamp should use this name convention.
So it will be easy for plugins to protect system fields in future.
The text was updated successfully, but these errors were encountered: