Skip to content

docs: renaming objects in Studio#50

Open
rnv812 wants to merge 3 commits into
developfrom
feat/rename-objects
Open

docs: renaming objects in Studio#50
rnv812 wants to merge 3 commits into
developfrom
feat/rename-objects

Conversation

@rnv812

@rnv812 rnv812 commented Jul 25, 2026

Copy link
Copy Markdown
Member

Documents the rename actions shipped in eventum-generator/eventum#200 (issue eventum-generator/eventum#174).

Studio pages

  • Projects — a "Renaming a project" section: the directory moves, instances follow the new name, and all of them must be stopped first. Also corrects the row-menu sentence, which listed a "duplicating" action the menu does not have.
  • Instances — renaming keeps the project, the parameters and the scenario membership; only inactive instances can be renamed, and logs written under the previous name stay in their own file.
  • Scenarios — the tag is rewritten on every instance carrying it, and the new name has to be free, so two scenarios cannot be merged by renaming one onto the other.
  • Settings and management — a "Renaming secrets" section: the button sits next to the secret name and the dialog lists the projects reading ${secrets.name}, which keep the old name.

TextCursorInput is registered in mdx-components.tsx for the rename icon used inline.

API reference

Re-exported public/schemas/eventum-openapi.json (the only path-level change is the five new endpoints; info.version moves 2.5.0 → 2.6.0) and regenerated the pages.

scripts/generate-docs.ts also needed a fix: with groupBy: 'route' the generated entries are nested under group entries and the index builder skips groups, so the default configuration produced an overview page with an empty card list — every endpoint link was dropped on regeneration. The script now names the flattened page paths explicitly, and content/docs/api/index.mdx is again taken from the generator as-is, carrying a card per endpoint (79 = 74 existing + 5 new).

pnpm build passes; the rendered overview page carries all 79 links, and the five endpoint pages plus the four Studio pages are in the static output.

🤖 Generated with Claude Code

rnv812 and others added 3 commits July 25, 2026 23:12
Re-export the OpenAPI schema and generate the pages for the four rename
endpoints and the secret-references endpoint.

`pnpm generate-api-docs` currently emits `content/docs/api/index.mdx`
with an empty card list - reproduced against the unchanged schema on
develop, so it predates this change. The index is kept as generated
before and the five cards are added in its format.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Describe each rename action where its page already covers the row
actions, including what cascades and what does not: instances follow a
renamed project and must be stopped, a renamed instance keeps its
scenario membership, a scenario tag is rewritten everywhere, and
`${secrets.*}` placeholders keep the old name.

Also corrects the projects row menu description, which listed a
"duplicating" action the menu does not have.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
With `groupBy: 'route'` the generated entries are nested under group
entries, and the index builder skips groups - left to its default the
overview page came out with an empty card list, dropping every endpoint
link. Naming the flattened page paths explicitly keeps a card per
endpoint, so `pnpm generate-api-docs` output can be taken as-is again.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant