-
Notifications
You must be signed in to change notification settings - Fork 649
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Redirect on updating questionnaire #10796
Redirect on updating questionnaire #10796
Conversation
WalkthroughThe changes update the Changes
Sequence Diagram(s)sequenceDiagram
participant QE as QuestionnaireEditor
participant UQ as updateQuestionnaire Mutation
participant Router as Navigation Service
QE->>UQ: Trigger updateQuestionnaire()
UQ-->>QE: Return QuestionnaireDetail data
QE->>Router: navigate(`/admin/questionnaire/${data.slug}`)
Possibly related PRs
Suggested labels
Suggested reviewers
Poem
✨ Finishing Touches
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
✅ Deploy Preview for care-ohc ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
src/components/Questionnaire/QuestionnaireEditor.tsx (1)
707-709
: Enhance error handling for better debugging and user experience.Consider improving the error handling by:
- Logging the error details for debugging
- Providing more specific error messages to users based on the error type
- Implementing retry logic for transient failures
- onError: (_error) => { - toast.error("Failed to update questionnaire"); - }, + onError: (error) => { + console.error("Failed to update questionnaire:", error); + const message = error.response?.data?.message || "Failed to update questionnaire"; + toast.error(message, { + description: "Please try again or contact support if the issue persists", + }); + },
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
src/components/Questionnaire/QuestionnaireEditor.tsx
(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (5)
- GitHub Check: Redirect rules - care-ohc
- GitHub Check: Header rules - care-ohc
- GitHub Check: Pages changed - care-ohc
- GitHub Check: cypress-run (1)
- GitHub Check: OSSAR-Scan
🔇 Additional comments (2)
src/components/Questionnaire/QuestionnaireEditor.tsx (2)
702-705
: LGTM! The navigation enhancement looks good.The implementation correctly uses the questionnaire's slug from the response data to navigate to the updated questionnaire's page, providing immediate feedback after a successful update.
704-704
: LGTM! Cache invalidation is properly implemented.The cache invalidation correctly targets the specific questionnaire detail query, ensuring the UI stays in sync with the backend data.
@Sulochan-khadka Your efforts have helped advance digital healthcare and TeleICU systems. 🚀 Thank you for taking the time out to make CARE better. We hope you continue to innovate and contribute; your impact is immense! 🙌 |
Proposed Changes
@ohcnetwork/care-fe-code-reviewers
Merge Checklist
Summary by CodeRabbit