Guide & Demo | 2.x docs | 1.x docs
This project will be no longer maintained. Its features are stable enough and works perfectly in Vue 2.x.
For those who are looking for a Vue 3.x version, try https://github.com/rlemaigre/vue3-promise-dialog
Promisify dialogs!
A typical and essential type of user interaction is dialogs. Dialogs are somehow similar to Promise. A dialog will eventually close. A Promise will eventually resolve. A dialog returns some data when it closes. So does Promise. It is time to put them together.
vue-modal-dialogs has the magic to turn dialogs into Promises. Developers can build and control dialogs a lot easier in Vue.js applications. Especially in some complicated situations like controlling multiple dialogs, nested dialogs, etc.
Feel free to open an issue or PR if you have any questions, problems, or new ideas.
# Use npm
npm install vue-modal-dialogs --save
# Use yarn
yarn add vue-modal-dialogsThen import and install vue-modal-dialogs as a Vue plugin:
import * as ModalDialogs from 'vue-modal-dialogs'
Vue.use(ModalDialogs) // No optionsModalDialogs.create creates a dialog function.
A dialog function is nothing but a function that returns a dialog promise.
The dialog function's arguments depends on the options you passed in the
ModalDialogs.create function.
function create (component: VueComponent, ...props: string[]): DialogFunction
function create (options: DialogOptions): DialogFunctionThe component option is the Vue component constructor for the dialog component.
It can be a Promise resolves with a Vue component constructor for supporting
async component.
The props option maps the arguments of the dialog function to the properties of
the dialog component. For example, if you call the dialog function like this:
// The props option is ['title', 'content']
const dialogFunction = create(SomeComponent, 'title', 'content')
dialogFunction('This is title', 'This is content', 'Extra argument')The dialog component will receive these properties:
{
title: 'This is title', // 1st argument
content: 'This is content', // 2nd argument
// Stores all arguments
arguments: ['This is title', 'This is content', 'Extra argument']
}If you just leave the props option empty, the dialog function's first argument
will become a 'data object' stores all the properties to pass into
the dialog component.
// The props option is [] (an empty array)
const dialogFunction = create(SomeComponent)
dialogFunction({
title: 'This is title',
content: 'This is content'
}, 'Extra argument')The dialog component will receive these properties:
{
title: 'This is title', // Data from the first argument
content: 'This is content',
// Stores all arguments
arguments: [{ title: 'This is title', content: 'This is content'}, 'Extra argument']
}This is useful when you have lots of properties. It is better to use an object instead of a long list of arguments. Remember to define all the properties in the dialog component! Otherwise no property will be received.
The wrapper option specifies which dialogs wrapper to render the dialog component.
The default value is 'default'. In most cases you do not need to set this option.
The dialog promise will reject when the specified wrapper is not found.
A dialogs wrapper is nothing but a slightly modified <transition-group> component.
<dialogs-wrapper> component should be placed into the root component of your
project (typically App.vue), in order to make sure the component will never be
destroied.
It have two main properties:
-
name: The name of the wrapper. It MUST be unique throughout the project. The default value isdefault. -
transition-name: Alias to thenameproperty of the<transition-group>component.
Everything other than these two properties, including event listeners,
will be directly passed into the underlying <transition-group> component.
You are free to use full-featured <transition-group> component.
You can create multiply wrappers at the same time. Dialogs will go into the
wrapper you specifies when calling create function (see the following section).
Usually one wrapper with a default name is enough for most cases.
Dialog components will be rendered into the dialogs wrapper when you call the dialog function.
Property definitions are optional since you have defined them in
ModalDialogs.create, unless you want to validate these properties.
Just define them inside the dialog component like other components.
However, if you would like to use data objects to pass properties, you must manually define all props in the dialog component.
There are some additional properties and methods available in the dialog component:
$close(): A 'callback'. Call this method when it is time to close the dialog, with the data you want to send back. It will resolve the dialog promise.$error(): It is the same to$closebut it rejects the Promise.arguments: An array contains everything you passed in the dialog function.
A dialog promise is a promise with some additional methods for controlling the dialog outside.
close(),error(): The same to the$close()and$error()in the dialog component.transition(): Returns a promise that resolves after the dialog's transition with the same value as the dialog promise.getInstance(): Returns a promise that resolves with the dialog component instance.
vue-modal-dialogs have partial support for TypeScript. Vue.js 2.5 or above is required if you are using TypeScript.
Specify argument types and the return type through generic:
import SomeComponent from './comp.vue'
interface ConfirmData {
title: string,
content: string
}
// (prop1: string, prop2: string) => Promise<any>
create<string, string>(SomeComponent, 'title', 'content')
// (prop1: string, prop2: string) => Promise<boolean>
create<string, string, boolean>(SomeComponent, 'title', 'content')
// (data: ConfirmData) => Promise<any>
create<ConfirmData>(SomeComponent)
// (data: ConfirmData) => Promise<boolean>
create<ConfirmData, boolean>(SomeComponent)Dialog components can be defined by extending the base class
DialogComponent<ReturnType> with the help of
vue-property-decorator.
The ReturnType generic argument indicates the type that the promise resolves.
TypeScript can infer this generic argument in ModalDialogs.create.
import { Prop, Component } from 'vue-property-decorator'
import { create, DialogComponent } from 'vue-modal-dialogs'
@Component
export default class SomeComponent extends DialogComponent<boolean> {
@Prop() title: string
@Prop() content: string
ok () {
this.$close(true)
}
render (h) {
// ...
}
}
// (data: ConfirmData) => Promise<boolean>
create<ConfirmData>(SomeComponent)- Instead of using the default export (
import ModalDialogs from "vue-modal-dialogs";) withVue.useuse the import all syntax (import * as ModalDialogs from "vue-modal-dialogs";) makeDialogis renamed tocreate.- The
dialogIdproperty is removed and kept internally. You might need to find another way to implement your requirement withoutdialogId.
Here are two major breaking changes:
-
An HTML element is inserted into the DOM automatically in 1.x. Then I create a new root Vue instance on it. This causes critical problem when using vue-modal-dialogs with vuex, vue-i18n, etc.
Remove all options in
Vue.use(ModalDialogs, ...)and add a<dialogs-wrapper>component into the root component, typicallyApp.vue, of your project. -
CSS z-index control are completely removed. If you need to control it, do it yourself. The
dialogIdprop can be used as an auto-increment z-index value. Bind it to your dialog component.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent