Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Toast component
See original GitHub issueIt could be useful to have a notification “toast” component, similar to the notify feature of UIkit.
Two components are needed:
- The toast component itself: a styled box that renders its
children. - A manager that would position the boxes and animate their enter / leave transitions.
Questions / thoughts:
Do we want to allow users to discard them by clicking on a close button? Or by clicking directly on the message? => no behavior on press for now.
Instead of closing a message being clicked, we could emit an event so that it could do something (like macOS notifications). => no behavior on press for now.
How does it translate on small screens? Apart from the appearance, we should probably only display one at a time. => see Jouni’s comment below
About the API, an approach could be to use a provider + a function like React toastify does.
To do:
- Visual design (@jounih).
- Toast component implementation.
- Manager implementation.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:3
- Comments:21 (9 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@drcmda Sorry for the gitcoinbot spam; we’ll snooze him again 😃. We’re a bit held up this week but saw that react-springs@6 was released last week so we’ll be migrating shortly!
@gitcoinbot still on it 😃 the component is finished, waiting for react-spring integration in Aragon.