feat(NotificationList) -Automates notification creation for list example - #329

Pull Request Test Coverage Report for Build 1283

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

Totals
Change from base Build 1266:	0.0%
Covered Lines:	1692
Relevant Lines:	2082

💛 - Coveralls

Hey @AllenBW, I think the root cause of this behavior is our use of array indices as keys. In this branch, if you change this to

key={notification.key}

the bug goes away. I also doubled checked this in V2V by using notification.data.id as keys in <NotificationList>, and things are now working as expected.

Not sure if this will help with our quickly disappearing toasts, but I think this takes care of this issue :)

Here are a couple links

1. Docs
2. Medium Article

@michaelkro Updated this example to mix a lil bit of original implementation with a more real world situation, and the bugfix yah mentioned! (storybook also updated)

this feels like more of a chore(NotificationList): Automates notification creation for list example since you are just touching .stories.js file? thanks for looking at this @AllenBW @michaelkro ! I'm good w/ the change otherwise...

@priley86 Reworded to chore! 😋

LGTM!