Skip to content

[US-3.1 / OBT-203] Create a language inline from the project form - #19

Open
levigtri wants to merge 3 commits into
mainfrom
levigft/obt-203-us-31-create-a-new-language-directly-from-the-project
Open

[US-3.1 / OBT-203] Create a language inline from the project form#19
levigtri wants to merge 3 commits into
mainfrom
levigft/obt-203-us-31-create-a-new-language-directly-from-the-project

Conversation

@levigtri

@levigtri levigtri commented Jul 5, 2026

Copy link
Copy Markdown
Member

Summary

US-3.1 / OBT-203 — Let users create a new language directly from the project creation/edit form, without navigating away to the Languages page and losing their progress.

Changes

  1. ProjectsPage.tsx: add a "New language" link next to the language selector that opens a nested dialog (Radix supports nested dialogs) with name and code fields.
  2. On save, handleCreateLanguage calls languagesAPI.create, invalidates and re-fetches the languages store, auto-selects the new language, and closes the nested dialog. The project form state (name, description) is preserved throughout.
  3. Duplicate-code (409) and generic errors are surfaced via toast.

Type of Change

  • Feature

Testing

  • npm run typecheck — pass
  • npm run lint — 0 errors (pre-existing ProjectsPage warning only)
  • npm run build — pass

Front-only — uses the existing languages API.

levigtri and others added 3 commits July 5, 2026 01:06
Add a "New language" action next to the language selector that opens a nested
dialog with name and code fields. On save it creates the language via the API,
refreshes the languages store, and auto-selects the new entry — the project form
state is preserved throughout. Duplicate-code errors are surfaced to the user.
The fetch-on-mount effect intentionally runs once; add
eslint-disable-next-line react-hooks/exhaustive-deps to match the
codebase convention (LanguagesPage) and clear the ESLint warning.

Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
@coderabbitai

coderabbitai Bot commented Jul 15, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@levigtri, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 41 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: QUIET

Plan: Pro Plus

Run ID: 85f05b67-a082-4f73-8ad9-0f789b5a292b

📥 Commits

Reviewing files that changed from the base of the PR and between 130fc4a and 287747f.

📒 Files selected for processing (1)
  • src/components/pages/ProjectsPage.tsx
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch levigft/obt-203-us-31-create-a-new-language-directly-from-the-project

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

@levigtri levigtri self-assigned this Jul 15, 2026
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