Allow MatSnackBarRef to be closed with an ActionValue

[angelaki]

Currently the Snackbar can only be dismiss'ed or dismissWithAction'ed. And the action cannot be passed! So if I have more than one action I need to store the result in a static scope (or am I mistaken?). Wouldn't it make much more sense to just have a dismiss-method with an optional value parameter? Like the MatDialog has?

This dismiss / dismissWithAction thing really feels dusty ...

[crisbeto]

I think that it limited on purpose, because snack bars are meant primarily for simple pieces of information that go away automatically after a certain amount of time, not for passing data around.

[angelaki]

In general I totally agree with you - but my scenario is quite plausible, too:

I show an event with a close button and an action. Now there are three scenarios absolutely relevant for me:

• snackbar hid unnoticed
• snackbar hid intentionally
• command was selected

With only action / no-action a cannot differentiate.

Guess that's a pretty common and justifiable usecase. So come on, give it a bit more prio 👍 Not at least since it costs absolutely no effort.

[crisbeto]

I'll add this for discussion in our next team meeting.

[jelbourn]

We discussed this and decided that this is a especially niche use case considering the snackbar's intended use in the Material Design spec. We'll leave it open at the lowest priority for now and revisit if there's more demand in the future.

[angelaki]

Ok, so I'll probably go on with my global variable. Eventhough I see no need to not just let the snackbar use a similar interface the dialog uses - it has no disadvantages.

[angular-robot]

Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends.

Find more details about Angular's feature request process in our documentation.

[angular-robot]

Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage.

We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package.

You can find more details about the feature request process in our documentation.