mtrl 0.8.0-next.7 → 0.8.0-next.8

package/dist/components/index.d.ts

@@ -35,6 +35,7 @@ export { createSegment } from "./segmented-button/segment";
 export { default as createSheet } from "./sheet";
 export { default as createSlider } from "./slider";
 export { default as createSnackbar } from "./snackbar";
+export { clearSnackbars } from "./snackbar";
 export { default as createSwitch } from "./switch";
 export { default as createTabs } from "./tabs";
 export { createTab } from "./tabs/tab";

package/dist/components/snackbar/index.d.ts

@@ -1,3 +1,4 @@
 export { default } from "./snackbar";
+export { clearSnackbars } from "./snackbar";
 export { SnackbarConfig, SnackbarComponent, SnackbarQueueBehavior, } from "./types";
 export { SNACKBAR_QUEUE_BEHAVIORS } from "./constants";

package/dist/components/snackbar/snackbar.d.ts

@@ -5,4 +5,13 @@ import { SnackbarConfig, SnackbarComponent } from './types';
  * @returns {SnackbarComponent} Snackbar component instance
  */
 declare const createSnackbar: (config: SnackbarConfig) => SnackbarComponent;
+/**
+ * Dismisses the snackbar on screen and drops the ones still waiting.
+ *
+ * Messages belong to the thing that raised them: a drawer that closes, an
+ * account that signs out. Without this the queue outlives them, so a message
+ * about a list nobody is looking at any more stays on screen, and, because the
+ * queue shows one at a time, the next message waits behind it.
+ */
+export declare const clearSnackbars: () => void;
 export default createSnackbar;

package/dist/components/snackbar/types.d.ts

@@ -177,6 +177,8 @@ export interface QueuedSnackbar {
     _show: () => void;
     /** Visually dismisses the snackbar without advancing the queue */
     _hide?: () => void;
+    /** The snackbar's own element, so the queue can tell whether it is still on screen */
+    element?: HTMLElement;
     on: (event: string, handler: () => void) => void;
     off: (event: string, handler: () => void) => void;
 }