-
Notifications
You must be signed in to change notification settings - Fork 2.8k
rename metadata reset to metadta clear (close #1851) #1893
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
Conversation
|
Deploy preview for hasura-docs ready! Built with commit b73a5af |
|
Review app for commit 25ca350 deployed to Heroku: https://hge-ci-pull-1893.herokuapp.com |
|
Review app for commit 4be117f deployed to Heroku: https://hge-ci-pull-1893.herokuapp.com |
|
Review app for commit b73a5af deployed to Heroku: https://hge-ci-pull-1893.herokuapp.com |
|
Review app https://hge-ci-pull-1893.herokuapp.com is deleted |
Description
The word "reset" is little ambiguous (reset to scratch or reset to last known consistent state). metadata reset clears the all the metadata to mimic a freshly installed hasura instance. This actually invokes the clear_metadata API in the backend and hence should also be called metadata clear for perfect clarity.
All references to metadata reset should be changed to metadata clear.
Affected components
Related Issues
#1851
Solution and Design
Changed main command name from reset to clear and added an alias reset.