Skip to content

fix(NotificationList) Reconfigure to clear the component set timeout - #328

Closed
AllenBW wants to merge 1 commit into
patternfly:masterfrom
AllenBW:bug/#327-dangling-notification
Closed

AllenBW wants to merge 1 commit into
patternfly:masterfrom
AllenBW:bug/#327-dangling-notification

Conversation

@AllenBW

@AllenBW AllenBW commented May 4, 2018 •

Copy link
Copy Markdown
Contributor

@coveralls

Copy link
Copy Markdown

Pull Request Test Coverage Report for Build 1273

  • 0 of 1 (0.0%) changed or added relevant line in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 74.251%

Changes Missing Coverage Covered Lines Changed/Added Lines %
src/components/ToastNotification/TimedToastNotification.js 0 1 0.0%
Totals Coverage Status
Change from base Build 1266: 0.0%
Covered Lines: 1692
Relevant Lines: 2082

💛 - Coveralls

@michaelkro

Copy link
Copy Markdown
Contributor

Please see #329 (comment)

@AllenBW

AllenBW commented May 7, 2018

Copy link
Copy Markdown
Contributor Author

Sounds good to me @michaelkro closing.. gonna update/keep the other one open, still might be nice to demonstrate a few different implementations of notification lists

@AllenBW AllenBW closed this May 7, 2018
@AllenBW
AllenBW deleted the bug/#327-dangling-notification branch May 7, 2018 12:52
@michaelkro

Copy link
Copy Markdown
Contributor

Definitely! My guess is your new example will be much closer to a real use case, since notifications will most likely be dynamically added to and removed from <ToastNotificationList>

We should def merge that one

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.

Dangling timed notification, (aka why won't that thing dismiss)

4 participants