Skip to content
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

fix(dashboard): Workflow saving status on toast and multiple toasts #6972

Merged
merged 2 commits into from
Nov 12, 2024

Conversation

desiprisg
Copy link
Contributor

What changed? Why was the change needed?

Screenshots

Screen.Recording.2024-11-12.at.5.46.53.PM.mov
Expand for optional sections

Related enterprise PR

Special notes for your reviewer

Copy link

linear bot commented Nov 12, 2024

Copy link

netlify bot commented Nov 12, 2024

Deploy Preview for novu-stg-vite-dashboard-poc ready!

Name Link
🔨 Latest commit 09f5962
🔍 Latest deploy log https://app.netlify.com/sites/novu-stg-vite-dashboard-poc/deploys/6733d22d734a2000087c7447
😎 Deploy Preview https://deploy-preview-6972--novu-stg-vite-dashboard-poc.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

onSuccess,
onError,
export const useUpdateWorkflow = (
options?: UseMutationOptions<WorkflowResponseDto, unknown, Parameters<typeof updateWorkflow>[0]>
Copy link
Contributor

Choose a reason for hiding this comment

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

IMO we should not expose the react-query options as we will be tied by it's interface, but rather expose ours with the needed functionality.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ideally, I wouldn't create a useUpdateWorkflow hook in general. If we create one hook per mutation/query, we are already tied by its interface. I don't see any difference.

Copy link
Contributor

Choose a reason for hiding this comment

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

the difference is that we will be free to change the implementation of the hook to whatever we want if we decide

@desiprisg desiprisg force-pushed the nv-4644-auto-save-icon-is-confusing branch from 31b303c to 789d8c9 Compare November 12, 2024 18:05
@LetItRock LetItRock merged commit 63bb3e6 into next Nov 12, 2024
31 of 32 checks passed
@LetItRock LetItRock deleted the nv-4644-auto-save-icon-is-confusing branch November 12, 2024 22:27
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.

3 participants