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.
If a notification is rendered more than once simultaneously, React throws a warning like this:
Using the index of the item instead of the options map as the key fixes the issue. It should be safe here since a notification component is never re-rendered.Further testing demonstrated the statement above false. Using the index as the key caused the notifications to get messed up in situations where multiple different notifications were rendered simultaneously.
Generating a UUID for each notification seems to work better.