Hyperblast
Hyperblast
Swagger currently does not support that, but we still can add it somehow. Probably pretend to be regular JSON, but describe actual behavior in comments.
This should be done differently. `NotificationGroup` should depend on `NotificationModel` and mounted by `index.js` similar to `App` view. This would allow easy testing in isolation.
Currently there are only three (small, medium, large), but some components require more flexible approach, e.g. let's each component register its own desired breakpoint and receive notifications via standard subscriptions.

This is useful for mobile layouts that have limited horizontal space.
It would be nice to have one for shell scripting and other high-level automation tasks. The most hard decision is the implementation language, the following table summarises pros and cons....
See for details https://github.com/krasimir/navigo/issues/172
Via notifications API https://developer.mozilla.org/en-US/docs/Web/API/Notifications_API