Skip to content

feat(dev-server): Add toast for successful sync and warning for failure#450

Merged
cdelst merged 1 commit intomainfrom
cdelst/FUN-195/add-toast-on-successful-sync-and-update
Oct 17, 2024
Merged

feat(dev-server): Add toast for successful sync and warning for failure#450
cdelst merged 1 commit intomainfrom
cdelst/FUN-195/add-toast-on-successful-sync-and-update

Conversation

@cdelst
Copy link
Contributor

@cdelst cdelst commented Oct 17, 2024

image

@cdelst cdelst requested a review from mike-zorn October 17, 2024 21:29
@cdelst cdelst changed the title feat: Add toast for successful sync and warning for failure feat(dev-server): Add toast for successful sync and warning for failure Oct 17, 2024
@@ -28,6 +29,7 @@ const Root = () => {
<React.StrictMode>
<IconProvider>
<App />

Choose a reason for hiding this comment

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

Should it be at the top? That's where most of the latent interactions happen.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

TBH, not sure. I think just having it somewhere relatively global is standard.

Don't think it matters that much here?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

wym by at the top?

Choose a reason for hiding this comment

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

oh like at the top of the page. Screenshot makes it look like maybe it's at the bottom of the page?

Choose a reason for hiding this comment

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

Location in the markup seems fine.

Copy link
Contributor Author

@cdelst cdelst Oct 17, 2024

Choose a reason for hiding this comment

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

ohhh, yea... bottom of the page is standard for toasts and I don't think We can change that. The ToastProvider doesn't actually control that either. The position is absolute no matter where we render the provider

Copy link
Contributor Author

Choose a reason for hiding this comment

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

When using it it's clear enough to give some confirmation 👍🏻

Choose a reason for hiding this comment

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

🆒

Copy link

@mike-zorn mike-zorn left a comment

Choose a reason for hiding this comment

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

One thought on placement, but 👍🏻

@cdelst cdelst merged commit 2831519 into main Oct 17, 2024
@cdelst cdelst deleted the cdelst/FUN-195/add-toast-on-successful-sync-and-update branch October 17, 2024 22:50
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