You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Snackbar, toast, notification and dialog as the messaging components are used frequently in development, which should be bound to vue prototype as a function, like element-ui. For example:
This won't be on the vue prototype, but we may implement a message queue in the snackbar component itself so you can manage them with something like Vuex.
@KaelWD Thanks a lot for the reply. I don't know exactly how you plan to design this message queue, but not all Vue.js projects use something like Vuex to share and store data. Even if in the message queue, developers should not add <v-snackbar> manually to every route-component / component / page, because almost everyone of them needs to deal messaging. I think binding it to Vue.prototype is an easy way to realize the expectation. Don't make it too complicate to use. PS: I agree that there should be only one snackbar shown in the same time.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. Please direct any non-bug questions to our Discord
lockbot
locked as resolved and limited conversation to collaborators
Apr 15, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
New Functionality
Snackbar, toast, notification and dialog as the messaging components are used frequently in development, which should be bound to vue prototype as a function, like element-ui. For example:
Improvements
So developers can give out a message easily by:
this.$message('v-snackbar', 'top', 'error', 'Bad response from server', true, 3000)
Bugs or Edge Cases it Helps Avoid
none
The text was updated successfully, but these errors were encountered: