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
happi rename
Add CLI entrypoint for easy renaming: $ happi rename at2l0 at2l0_foobar or perhaps $ happi rename at2l0=at2l0_foobar at1k4=at1k4_foobar
$ happi rename at2l0 at2l0_foobar
$ happi rename at2l0=at2l0_foobar at1k4=at1k4_foobar
This would update the 'name' field, the internal '_id', and the parent JSON db key for that backend
I believe this is how it'll work as-is, but correct me if not:
happi edit
happi repair
Add new rename command and fix up happi edit The backends may need a corresponding function for renaming
rename
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Expected Behavior
Add CLI entrypoint for easy renaming:
$ happi rename at2l0 at2l0_foobar
or perhaps
$ happi rename at2l0=at2l0_foobar at1k4=at1k4_foobar
This would update the 'name' field, the internal '_id', and the parent JSON db key for that backend
Current Behavior
I believe this is how it'll work as-is, but correct me if not:
happi edit
happi repair
(post ENH: Match Name to ID Field #327) will reset the name to the id in the case of the JSON backendPossible Solution
Add new
rename
command and fix uphappi edit
The backends may need a corresponding function for renaming
The text was updated successfully, but these errors were encountered: