A small library that serves as an abstraction layer for creating medium complex dialogs (containing options a user can choose, not only things like error messages...) in plugins for Adobe XD CC.

There are two main ways you can install the library.

1. With a package manager: If you're using a package manager for your plugin (npm or yarn), you can easily install the helper by running npm install xd-dialog-helper --save or yarn add xd-dialog-helper in your console inside your plugin's folder.
2. If you don't use a package manager, you can simply copy the dialog-helper.js-file from this repo into your project (e.g. into a lib-folder) and reference it that way.

Depending on which option you chose when installing the library, you can get a reference to the helper class in different ways:

If you installed it via a package manager and use some module bundler (like e.g., webpack), you can get a reference to the helper by using

const dialogHelper = require('xd-dialog-helper');

If you copied the dialog-helper.js file from the repo, you can reference it by using the relative path. Assuming, that your plugin's .js file is at the root level and you have a lib folder containing the helper (i.e. lib/dialog-helper.js), you can reference the helper by using

const dialogHelper = require('./lib/dialog-helper');

You can find a detailed guide on how to use the library in the repository wiki.

Mostly, there should be no breaking changes (but many additional options and improvements) in v1.0, since it mostly consists of an internal restructuring.

However, with the release of the new version, the types have moved to a types namespace inside the xd-dialog-helper module.

This means that instead of writing

dialogHelper.showDialog('dialog', 'My dialog', [{
    id: 123,
    type: dialogHelper.TEXT_INPUT,
    label: 'Good morning'
}]);

we have to write:

dialogHelper.showDialog('dialog', 'My dialog', [{
    id: 123,
    type: dialogHelper.types.TEXT_INPUT,
    label: 'Good morning'
}]);

Please note: The old way is still available (but marked as deprecated) in the alpha- and beta versions of v1.0. It will, however, get removed with the full release of the new version.

Also, the type constant previously were aliases for numeric constants representing the type. This is no longer the case (to support custom types), which is why numeric values are no longer possible for the type field.