Skip to content

chore: ui descriptions cleanup - #5493

Merged
akshaydeo merged 4 commits into
devfrom
07-23-chore_ui_descriptions_cleanup
Jul 23, 2026
Merged

akshaydeo merged 4 commits into
devfrom
07-23-chore_ui_descriptions_cleanup

Conversation

@roroghost17

@roroghost17 roroghost17 commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

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
  • Chore/CI

Affected areas

  • Core (Go)
  • Transports (HTTP)
  • Providers/Integrations
  • Plugins
  • UI (React)
  • Docs

How to test

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
  • 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

@coderabbitai

coderabbitai Bot commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Walkthrough

Changes

UI copy updates

Layer / File(s) Summary
Diagnostics and logging copy
ui/app/pprof/page.tsx, ui/app/workspace/config/views/loggingView.tsx, ui/app/workspace/observability/fragments/*
Updates heap allocation, leak, logging, and request-header descriptions.
MCP configuration and session copy
ui/app/workspace/config/views/mcpView.tsx, ui/app/workspace/mcp-registry/..., ui/app/workspace/mcp-sessions/views/sessionsTable.tsx
Revises MCP warnings, helper text, OAuth messaging, and session tooltips.
Workspace form and routing copy
ui/app/workspace/governance/..., ui/app/workspace/model-catalog/..., ui/app/workspace/providers/..., ui/app/workspace/routing-rules/..., ui/app/workspace/virtual-keys/...
Adjusts labels, validation messages, tooltips, and alerts across workspace forms.
Payload and shared feedback copy
ui/app/workspace/logs/sheets/logDetailView.tsx, ui/components/prompts/context.tsx, ui/components/ui/multibudgets.tsx
Reformats large-payload warnings and updates shared error and validation messages.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Suggested reviewers: impoiler, pratham-mishra04

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 13.33% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Title check ✅ Passed The title is concise and accurately summarizes the PR's main UI copy cleanup.
Description check ✅ Passed The description follows the template closely and includes the key sections; only the checklist is left unfilled, which is non-critical.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch 07-23-chore_ui_descriptions_cleanup

Comment @coderabbitai help to get the list of available commands.

@CLAassistant

CLAassistant commented Jul 23, 2026

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

roroghost17 commented Jul 23, 2026

Copy link
Copy Markdown
Contributor Author

@roroghost17
roroghost17 marked this pull request as ready for review July 23, 2026 11:02

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

📥 Commits

Reviewing files that changed from the base of the PR and between c019b24 and 03a0b73.

📒 Files selected for processing (20)
  • ui/app/pprof/page.tsx
  • ui/app/workspace/config/views/loggingView.tsx
  • ui/app/workspace/config/views/mcpView.tsx
  • ui/app/workspace/governance/views/teamSheet.tsx
  • ui/app/workspace/logs/sheets/logDetailView.tsx
  • ui/app/workspace/mcp-registry/library/views/mcpLibraryAddServerSheet.tsx
  • ui/app/workspace/mcp-registry/views/oauth2Authorizer.tsx
  • ui/app/workspace/mcp-sessions/views/sessionsTable.tsx
  • ui/app/workspace/model-catalog/views/attributeSheet.tsx
  • ui/app/workspace/observability/fragments/maximFormFragment.tsx
  • ui/app/workspace/observability/fragments/otelFormFragment.tsx
  • ui/app/workspace/providers/fragments/betaHeadersFormFragment.tsx
  • ui/app/workspace/providers/fragments/deploymentsTable.tsx
  • ui/app/workspace/providers/views/modelProviderKeysTableView.tsx
  • ui/app/workspace/routing-rules/tree/views/node/rfRuleNode.tsx
  • ui/app/workspace/routing-rules/tree/views/routingTreeView.tsx
  • ui/app/workspace/routing-rules/views/routingRuleSheet.tsx
  • ui/app/workspace/virtual-keys/views/virtualKeySheet.tsx
  • ui/components/prompts/context.tsx
  • ui/components/ui/multibudgets.tsx

Comment thread ui/app/workspace/routing-rules/views/routingRuleSheet.tsx
coderabbitai[bot]
coderabbitai Bot previously approved these changes Jul 23, 2026
akshaydeo
akshaydeo previously approved these changes Jul 23, 2026

akshaydeo commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

Merge activity

@akshaydeo
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
akshaydeo changed the base branch from graphite-base/5493 to dev July 23, 2026 16:04
@akshaydeo
akshaydeo dismissed stale reviews from coderabbitai[bot] and themself July 23, 2026 16:04

The base branch was changed.

@akshaydeo
akshaydeo merged commit 3801edc into dev Jul 23, 2026
9 of 10 checks passed
@akshaydeo
akshaydeo deleted the 07-23-chore_ui_descriptions_cleanup branch July 23, 2026 16:05
@coderabbitai coderabbitai Bot mentioned this pull request Jul 24, 2026
18 tasks
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
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.

3 participants