Conversation
github-actions
bot
added
the
Scope: Frontend
cvxluo
force-pushed
the
cvxluo/surface-slug-validation-errors-on-org-settings-for
branch
from
85fff20 to
eca6f40
Compare
cvxluo
force-pushed
the
cvxluo/surface-slug-validation-errors-on-org-settings-for
branch
from
eca6f40 to
853b44e
Compare
cvxluo
force-pushed
the
cvxluo/surface-slug-validation-errors-on-org-settings-for
branch
from
853b44e to
b59ed09
Compare
When changing the org slug to one already in use, the backend returns a field-level error but the frontend was showing a generic 'Unable to save change' toast. This was a regression from the form migration to TanStack which landed after the backend fix. Use setFieldErrors to display the API validation message inline on the slug field instead of swallowing it. Co-authored-by: Claude <noreply@anthropic.com>
cvxluo
force-pushed
the
cvxluo/surface-slug-validation-errors-on-org-settings-for
branch
from
b59ed09 to
2273d66
Compare
cvxluo
deleted the
cvxluo/surface-slug-validation-errors-on-org-settings-for
branch
george-sentry
pushed a commit
that referenced
this pull request
Apr 9, 2026
…112556) When changing the org slug to one already in use, the backend returns a field-level error but the frontend was showing a generic 'Unable to save change' toast. This was a regression from the form migration to TanStack which landed after the backend fix. Use setFieldErrors to display the API validation message inline on the slug field instead of swallowing it. <img width="1196" height="260" alt="Screenshot 2026-04-08 at 6 00 26 PM" src="https://github.com/user-attachments/assets/77af01f0-f9b9-4fca-ab64-5754be786036" /> I kept the toast showing up so this diff remains small. Fixes #112376 Co-authored-by: Claude <noreply@anthropic.com>
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
2 participants
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.
When changing the org slug to one already in use, the backend returns a field-level error but the frontend was showing a generic 'Unable to save change' toast. This was a regression from the form migration to TanStack which landed after the backend fix.
Use setFieldErrors to display the API validation message inline on the slug field instead of swallowing it.
I kept the toast showing up so this diff remains small.
Fixes #112376