chore: ui descriptions cleanup - #5493
Merged
Merged
Conversation
Contributor
📝 WalkthroughWalkthroughChangesUI copy updates
Estimated code review effort: 1 (Trivial) | ~5 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
This was referenced Jul 23, 2026
Contributor
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@ui/app/workspace/routing-rules/views/routingRuleSheet.tsx`:
- Line 366: Update the user-facing text near the rule-composition description to
add a comma after “e.g.”, so it reads “e.g., normalize a model alias first”
while preserving the rest of the wording.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro Plus
Run ID: d0275e66-e468-4b80-8f4e-491e98c22ec9
📒 Files selected for processing (20)
ui/app/pprof/page.tsxui/app/workspace/config/views/loggingView.tsxui/app/workspace/config/views/mcpView.tsxui/app/workspace/governance/views/teamSheet.tsxui/app/workspace/logs/sheets/logDetailView.tsxui/app/workspace/mcp-registry/library/views/mcpLibraryAddServerSheet.tsxui/app/workspace/mcp-registry/views/oauth2Authorizer.tsxui/app/workspace/mcp-sessions/views/sessionsTable.tsxui/app/workspace/model-catalog/views/attributeSheet.tsxui/app/workspace/observability/fragments/maximFormFragment.tsxui/app/workspace/observability/fragments/otelFormFragment.tsxui/app/workspace/providers/fragments/betaHeadersFormFragment.tsxui/app/workspace/providers/fragments/deploymentsTable.tsxui/app/workspace/providers/views/modelProviderKeysTableView.tsxui/app/workspace/routing-rules/tree/views/node/rfRuleNode.tsxui/app/workspace/routing-rules/tree/views/routingTreeView.tsxui/app/workspace/routing-rules/views/routingRuleSheet.tsxui/app/workspace/virtual-keys/views/virtualKeySheet.tsxui/components/prompts/context.tsxui/components/ui/multibudgets.tsx
akshaydeo
previously approved these changes
Jul 23, 2026
Contributor
Merge activity
|
akshaydeo
changed the base branch from
07-23-chore_update_otel_test_harness_with_error_scenarios
to
graphite-base/5493
July 23, 2026 16:04
akshaydeo
dismissed stale reviews from coderabbitai[bot] and themself
July 23, 2026 16:04
The base branch was changed.
akshaydeo
pushed a commit
that referenced
this pull request
Jul 24, 2026
## Summary Replaces em-dash (`—`) separators used as clause connectors in UI copy with grammatically appropriate alternatives: semicolons, colons, commas, or periods. This improves readability and consistency across tooltips, descriptions, labels, alerts, and inline help text throughout the UI. ## Changes - Replaced em-dashes used to join independent clauses with semicolons (e.g. "token is not revoked at the provider — it stays detached" → "...provider; it stays detached") - Replaced em-dashes used to introduce elaborations or examples with colons or commas (e.g. "Large payload request — input content..." → "Large payload request: input content...") - Replaced em-dashes used in parenthetical asides with parentheses or commas where appropriate - Changed one em-dash team name separator in a combobox label to a standard hyphen (`-`) since it appears in a data label context rather than prose ## Type of change - [ ] Bug fix - [ ] Feature - [ ] Refactor - [ ] Documentation - [x] Chore/CI ## Affected areas - [ ] Core (Go) - [ ] Transports (HTTP) - [ ] Providers/Integrations - [ ] Plugins - [x] UI (React) - [ ] Docs ## How to test ```sh cd ui pnpm i || npm i pnpm build || npm run build ``` Visually inspect affected UI surfaces (logging config, MCP config, routing rules, virtual keys, provider keys, pprof page, log detail view, sessions table, observability fragments) to confirm copy reads correctly with no regressions. ## Screenshots/Recordings No visual layout changes expected; only text content is affected. ## Breaking changes - [ ] Yes - [x] No ## Related issues ## Security considerations None. ## Checklist - [ ] I read `docs/contributing/README.md` and followed the guidelines - [ ] I added/updated tests where appropriate - [ ] I updated documentation where needed - [ ] I verified builds succeed (Go and UI) - [ ] I verified the CI pipeline passes locally if applicable
akhsaul
pushed a commit
to akhsaul/bifrost
that referenced
this pull request
Aug 27, 2026
## Summary Replaces em-dash (`—`) separators used as clause connectors in UI copy with grammatically appropriate alternatives: semicolons, colons, commas, or periods. This improves readability and consistency across tooltips, descriptions, labels, alerts, and inline help text throughout the UI. ## Changes - Replaced em-dashes used to join independent clauses with semicolons (e.g. "token is not revoked at the provider — it stays detached" → "...provider; it stays detached") - Replaced em-dashes used to introduce elaborations or examples with colons or commas (e.g. "Large payload request — input content..." → "Large payload request: input content...") - Replaced em-dashes used in parenthetical asides with parentheses or commas where appropriate - Changed one em-dash team name separator in a combobox label to a standard hyphen (`-`) since it appears in a data label context rather than prose ## Type of change - [ ] Bug fix - [ ] Feature - [ ] Refactor - [ ] Documentation - [x] Chore/CI ## Affected areas - [ ] Core (Go) - [ ] Transports (HTTP) - [ ] Providers/Integrations - [ ] Plugins - [x] UI (React) - [ ] Docs ## How to test ```sh cd ui pnpm i || npm i pnpm build || npm run build ``` Visually inspect affected UI surfaces (logging config, MCP config, routing rules, virtual keys, provider keys, pprof page, log detail view, sessions table, observability fragments) to confirm copy reads correctly with no regressions. ## Screenshots/Recordings No visual layout changes expected; only text content is affected. ## Breaking changes - [ ] Yes - [x] No ## Related issues ## Security considerations None. ## Checklist - [ ] I read `docs/contributing/README.md` and followed the guidelines - [ ] I added/updated tests where appropriate - [ ] I updated documentation where needed - [ ] I verified builds succeed (Go and UI) - [ ] I verified the CI pipeline passes locally if applicable
occcat
pushed a commit
to occcat/bifrost
that referenced
this pull request
Sep 2, 2026
## Summary Replaces em-dash (`—`) separators used as clause connectors in UI copy with grammatically appropriate alternatives: semicolons, colons, commas, or periods. This improves readability and consistency across tooltips, descriptions, labels, alerts, and inline help text throughout the UI. ## Changes - Replaced em-dashes used to join independent clauses with semicolons (e.g. "token is not revoked at the provider — it stays detached" → "...provider; it stays detached") - Replaced em-dashes used to introduce elaborations or examples with colons or commas (e.g. "Large payload request — input content..." → "Large payload request: input content...") - Replaced em-dashes used in parenthetical asides with parentheses or commas where appropriate - Changed one em-dash team name separator in a combobox label to a standard hyphen (`-`) since it appears in a data label context rather than prose ## Type of change - [ ] Bug fix - [ ] Feature - [ ] Refactor - [ ] Documentation - [x] Chore/CI ## Affected areas - [ ] Core (Go) - [ ] Transports (HTTP) - [ ] Providers/Integrations - [ ] Plugins - [x] UI (React) - [ ] Docs ## How to test ```sh cd ui pnpm i || npm i pnpm build || npm run build ``` Visually inspect affected UI surfaces (logging config, MCP config, routing rules, virtual keys, provider keys, pprof page, log detail view, sessions table, observability fragments) to confirm copy reads correctly with no regressions. ## Screenshots/Recordings No visual layout changes expected; only text content is affected. ## Breaking changes - [ ] Yes - [x] No ## Related issues ## Security considerations None. ## Checklist - [ ] I read `docs/contributing/README.md` and followed the guidelines - [ ] I added/updated tests where appropriate - [ ] I updated documentation where needed - [ ] I verified builds succeed (Go and UI) - [ ] I verified the CI pipeline passes locally if applicable
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Summary
Replaces em-dash (
—) separators used as clause connectors in UI copy with grammatically appropriate alternatives: semicolons, colons, commas, or periods. This improves readability and consistency across tooltips, descriptions, labels, alerts, and inline help text throughout the UI.Changes
-) since it appears in a data label context rather than proseType of change
Affected areas
How to test
Visually inspect affected UI surfaces (logging config, MCP config, routing rules, virtual keys, provider keys, pprof page, log detail view, sessions table, observability fragments) to confirm copy reads correctly with no regressions.
Screenshots/Recordings
No visual layout changes expected; only text content is affected.
Breaking changes
Related issues
Security considerations
None.
Checklist
docs/contributing/README.mdand followed the guidelines