On this page
Kater CLI Build an analysis
kater rename
Renames a field or an object in every place that names it, in every folder, as one change.
Without --write it shows the preview and changes nothing. Name what to rename by the natural key that a field’s card shows, by an object’s key, or by the path of its file.
Examples
# See every place a rename of a shared field changeskater rename semantic.marketing_sessions.sessions session_count# Rename itkater rename semantic.marketing_sessions.sessions session_count --write# Bring the rename to your local copykater git pullArguments
Options
It also takes the global options --json, --kater-root and --help.
The preview
- Each place that you can open, by folder, file and line, with the line as it reads after the rename and the new name marked.
- What moves. A query’s file and a workspace’s folder, with its dashboard and its grants, take the new name.
- The places in folders that you cannot open, as a count only. Kater writes them for you.
- What keeps its words, such as a label or a name that the field picker made.
- A name that is taken stops the rename. Kater shows it in red, then “Nothing changed.”
What it answers
With --write it gives the files it changed and the change’s id. kater undo with that id takes the whole rename back.
- A query or a chart named without its workspace is found in the workspace that you work in, then in every workspace that you can open. When two have that name, give its path.
- Something that you cannot open is not found, as for something that does not exist.
- A rename that changes other people’s folders is written by Kater’s worker. The command waits for it and says so.
- Agents ask first. An agent shows you the preview, and runs
--writewithkater_applyonly after you say yes. - In your own terminal, it renames in Kater, so it needs
kater login.kater git pullbrings the rename to your local copy.