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

Temp Component: Toast #106

Closed
Tracked by #95
huntabyte opened this issue Jun 10, 2023 · 2 comments
Closed
Tracked by #95

Temp Component: Toast #106

huntabyte opened this issue Jun 10, 2023 · 2 comments
Labels
status: under review Further discussion is needed to determine this issue's scope and/or implementation type: feature Introduction of new functionality to the application

Comments

@huntabyte
Copy link
Owner

huntabyte commented Jun 10, 2023

This issue will be used to track the identification and integration of a temporary Toast component. See #95 for more details.

@huntabyte huntabyte added type: feature Introduction of new functionality to the application status: under review Further discussion is needed to determine this issue's scope and/or implementation labels Jun 10, 2023
@alexanderscpo
Copy link

Hello, I would like to contribute to this feature. My plan is to maintain the same philosophy shadcn/ui: Toast -> svelte.

@huntabyte
Copy link
Owner Author

huntabyte commented Jun 11, 2023

Hey there @alexanderscpo !

I'm cool with letting you run with this, but I want to emphasize that we don't want to create and maintain our own headless toast component if that makes sense. Ideally we'd find a solid headless toast and wrap it in our styles/API structure.

The biggest thing for me is that it it aligns with this ARIA design pattern, and has most of the same capabilities as Radix UI's Toast Primitive.

Before writing any code, ensure to let us know your plan / high-level implementation idea so that you aren't wasting valuable time 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: under review Further discussion is needed to determine this issue's scope and/or implementation type: feature Introduction of new functionality to the application
Projects
Status: Done
Development

No branches or pull requests

2 participants