Skip to content

Conversation

@Subhan-Asghar
Copy link

@Subhan-Asghar Subhan-Asghar commented Jul 20, 2025

Fix: Resolve issue #1748 – Label creation now auto-refreshes the list after successful mutation
Previously, the new label was added successfully but the label list did not update automatically, requiring a manual page refresh. This has been fixed by triggering a query refetch when the label creation promise resolves.

Type of Change

  • 🐛 Bug fix (non-breaking change which fixes an issue)

Areas Affected

  • User Interface/Experience

Testing Done

  • Manual testing performed

Security Considerations

  • No sensitive data is exposed

Checklist

  • I have read the CONTRIBUTING document
  • My code follows the project's style guidelines
  • I have performed a self-review of my code
  • I have commented my code, particularly in complex areas
  • My changes generate no new warnings
  • All tests pass locally

Additional Notes

This resolves issue #1748 where newly created labels did not appear automatically. The label list is now refreshed upon successful creation without requiring a manual page reload.

Screenshots/Recordings

Add screenshots or recordings here if applicable.


By submitting this pull request, I confirm that my contribution is made under the terms of the project's license.


Summary by cubic

Fixed an issue where new labels did not appear automatically after creation by refreshing the label list once the label is added.

Summary by CodeRabbit

  • Bug Fixes
    • Improved label creation workflow to ensure label data is refreshed immediately after a new label is added.

Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 20, 2025

Walkthrough

The NavMain component's label creation logic is updated so that after a new label is created, the label data is immediately refreshed by calling refetch(). The refetch logic is moved from the LabelDialog's onSuccess prop to the onSubmit handler, ensuring data consistency after label creation.

Changes

File(s) Change Summary
apps/mail/components/ui/nav-main.tsx Updated label creation flow: chained refetch() after createLabel(data) in onSubmit; removed onSuccess={refetch} from LabelDialog.

Estimated code review effort

1 (<30 minutes)

Suggested reviewers

  • MrgSub

Poem

A label is born, then data anew,
The rabbit ensures the freshest view.
Refetch now hops in, right on cue—
No stale old lists, just something new!
With every click, the labels grow,
And bunnies keep the inbox flow.
🐇✨


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ca283cc and 59c49da.

📒 Files selected for processing (1)
  • apps/mail/components/ui/nav-main.tsx (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • apps/mail/components/ui/nav-main.tsx
✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

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

cubic analysis

1 issue found across 1 file • Review in cubic

React with 👍 or 👎 to teach cubic. You can also tag @cubic-dev-ai to give feedback, ask questions, or re-run the review.


const onSubmit = async (data: LabelType) => {
toast.promise(createLabel(data), {
toast.promise(createLabel(data).then(()=> refetch()), {
Copy link
Contributor

Choose a reason for hiding this comment

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

Passing refetch() as the resolved value changes the promise chain so that any failure of refetch() will cause the entire toast.promise to reject, showing “Failed to create label” even though the label was created successfully.

Prompt for AI agents
Address the following comment on apps/mail/components/ui/nav-main.tsx at line 175:

<comment>Passing refetch() as the resolved value changes the promise chain so that any failure of refetch() will cause the entire toast.promise to reject, showing “Failed to create label” even though the label was created successfully.</comment>

<file context>
@@ -172,7 +172,7 @@ export function NavMain({ items }: NavMainProps) {
   );
 
   const onSubmit = async (data: LabelType) =&gt; {
-    toast.promise(createLabel(data), {
+    toast.promise(createLabel(data).then(()=&gt; refetch()), {
       loading: &#39;Creating label...&#39;,
       success: &#39;Label created successfully&#39;,
       error: &#39;Failed to create label&#39;,
@@ -253,7 +253,6 @@ export function NavMain({ items }: NavMainProps) {
                       &lt;/Button&gt;
                     }
                     onSubmit={onSubmit}
-                    onSuccess={refetch}
                   /&gt;
                 ) : activeAccount?.providerId === &#39;microsoft&#39; ? null : null}
               &lt;/div&gt;
</file context>
Suggested change
toast.promise(createLabel(data).then(()=> refetch()), {
toast.promise(createLabel(data).then((res) => { refetch(); return res; }), {

refetch();
}), {
loading: 'Creating label...',
success: 'Label created successfully',
Copy link
Collaborator

Choose a reason for hiding this comment

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

toast.promise has a key finally, your promise doesn't even need to be called in the first argument

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.

2 participants