fix(group): improve error handling and navigation for slug changes #347
Conversation
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
- Show specific error message when slug is already in use (409 conflict) - Highlight slug field with error state when conflict occurs - Add handling for 403 (forbidden) and 422 (validation) errors - Navigate to public GroupPage after edit instead of staying on edit form This improves UX by: 1. Showing clear error messages for slug conflicts 2. Scrolling to and highlighting the slug field on error 3. Taking users to view their changes after saving instead of staying on the edit form Update navigation tests to reflect new behavior.
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
Changes
Error Handling (
GroupFormComponent.vue)Navigation (
useNavigation.ts)Test plan
Related to: OpenMeet-Team/openmeet-api#444