This repository was archived by the owner on Jan 22, 2026. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
Added persistent state for notifications and made default timeout 2.5s #82
Merged
sheridanvk
merged 1 commit into
master
from
sheridan/ch8668/make-default-for-notifications-2-5s-timeout
Feb 5, 2020
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do you think the
persistentprop collides with thetimeoutprop? for example:looking through the code it seems like the example will be persistent, but is that clear from where we are using the component? we could avoid this by saying
timeout={null | undefined | 0}means persistent, but i'm not sure that's very clear either!There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah this is something I struggled with - the previous definition has timeout = 0 as persistent, but that didn't feel great to me. I can add a custom function to the
persistentPropType which throws an error ifpersistent === trueandtimeout > 0; what do you think?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do you think a notification would ever be conditionally persistent? if we threw an error, then something like
<Notification persistent={shouldBePersistent} timeout={5000} />would need to be<Notification persistent={shouldBePersistent} timeout={shouldBePersistent === false ? 5000 : 0} />so that we don't pass in something invalid.maybe a wild idea: what if it was something like
timeout="never"to disable the timeout?