Sorry, no results found for "".

Plugin SDK > Opening modals

Opening modals

Within all the renderXXX hooks — that is, those that have the task of presenting a custom interface part to the user — it is possible to open custom modal dialogs to "get out" of the reduced space that the iframe provides, and get more room to build more complex interfaces.

Suppose our plugin implements a custom page accessible from the top navigation bar:

import React from 'react';
import ReactDOM from 'react-dom';
import { connect, MainNavigationTabsCtx, RenderPageCtx } from 'datocms-plugin-sdk';
import { Canvas } from 'datocms-react-ui';
function render(component: React.ReactNode) {
ReactDOM.render(
<React.StrictMode>{component}</React.StrictMode>,
document.getElementById('root'),
);
}
connect({
mainNavigationTabs(ctx: MainNavigationTabsCtx) {
return [
{
label: 'Welcome',
icon: 'igloo',
pointsTo: {
pageId: 'welcome',
},
},
];
},
renderPage(pageId, ctx: RenderPageCtx) {
switch (pageId) {
case 'welcome':
return render(<WelcomePage ctx={ctx} />);
}
},
});
type PropTypes = {
ctx: RenderPageCtx;
};
function WelcomePage({ ctx }: PropTypes) {
return <Canvas ctx={ctx}>Hi!</Canvas>;
}

Within the ctx argument you can find the function openModal(), which triggers the opening of a modal:

import { Canvas, Button } from 'datocms-react-ui';
function WelcomePage({ ctx }: PropTypes) {
const handleOpenModal = async () => {
const result = await ctx.openModal({
id: 'customModal',
title: 'Custom title!',
width: 'l',
parameters: { name: 'Mark' },
});
ctx.notice(result);
};
return (
<Canvas ctx={ctx}>
<Button type="button" onClick={handleOpenModal}>
Open modal!
</Button>
</Canvas>
);
}

The openModal() function offers various rendering options, for example you can set its size and title. Interestingly, the function returns a promise, which will be resolved when the modal is closed by the user.

You can specify what to render inside the modal by implementing a new hook called renderModal which, similarly to what we did with custom pages, initializes React with a custom component:

connect({
renderModal(modalId: string, ctx: RenderModalCtx) {
switch (modalId) {
case 'customModal':
return render(<CustomModal ctx={ctx} />);
}
},
});

You are free to fill the modal with the information you want, and you can access the parameters specified when opening the modal through ctx.parameters:

import { Canvas } from 'datocms-react-ui';
type PropTypes = {
ctx: RenderModalCtx;
};
function CustomModal({ ctx }: PropTypes) {
return (
<Canvas ctx={ctx}>
<div style={{ fontSize: 'var(--font-size-xxxl)', fontWeight: '500' }}>
Hello {ctx.parameters.name}!
</div>
</Canvas>
);
}

As with any other hook, it is important to wrap the content inside the Canvas component, so that the iframe will continuously auto-adjust its size based on the content we're rendering, and to give our app the look and feel of the DatoCMS web app.

Closing the modal

If the modal will be closed through the close button provided by the interface, the promise openModal() will be resolved with value null.

You can also decide not to show a "close" button:

const result = await sdk.openModal({
id: 'customModal',
// ...
closeDisabled: true,
});

In this case the user will only be able to close the modal via an interaction of your choice (custom buttons, for example):

import { Canvas, Button } from 'datocms-react-ui';
function CustomModal({ ctx }: PropTypes) {
const handleClose = (returnValue: string) => {
ctx.resolve(returnValue);
};
return (
<Canvas ctx={ctx}>
Hello {ctx.parameters.name}!
<Button type="button" onClick={handleClose.bind(null, 'a')}>Close A</Button>
<Button type="button" onClick={handleClose.bind(null, 'b')}>Close B</Button>
</Canvas>;
}

The ctx.resolve() function will close the modal, and resolve the original openModal() promise with the value you passed.

renderModal(modalId: string, ctx)

This function will be called when the plugin requested to open a modal (see the openModal hook).

Context object

The following properties and methods are available in the ctx argument:

Hook-specific properties and methods

This hook exposes additional information and operations specific to the context in which it operates.

ctx.modalId: string The ID of the modal that needs to be rendered.

The ID of the modal that needs to be rendered.

View on Github
ctx.parameters: Record<string, unknown> The arbitrary parameters of the modal declared in the openModal function.

The arbitrary parameters of the modal declared in the openModal function.

View on Github
ctx.resolve(returnValue: unknown) => Promise<void> A function to be called by the plugin to close the modal. The openModal call will be resolved with the passed return value.

A function to be called by the plugin to close the modal. The openModal call will be resolved with the passed return value.

View on Github
const returnValue = prompt(
'Please specify the value to return to the caller:',
'success',
);
await ctx.resolve(returnValue);
Properties and methods available in every hook

Every hook available in the Plugin SDK shares the same minumum set of properties and methods.

Authentication properties
Information about the current user using the CMS.
ctx.currentUser: User | SsoUser | Account | Organization The current DatoCMS user. It can either be the owner or one of the collaborators (regular or SSO).

The current DatoCMS user. It can either be the owner or one of the collaborators (regular or SSO).

View on Github
ctx.currentRole: Role The role for the current DatoCMS user.

The role for the current DatoCMS user.

View on Github
ctx.currentUserAccessToken: string | undefined The access token to perform API calls on behalf of the current user. Only available if currentUserAccessToken additional permission is granted.

The access token to perform API calls on behalf of the current user. Only available if currentUserAccessToken additional permission is granted.

View on Github
Custom dialog methods
These methods can be used to open custom dialogs/confirmation panels.
ctx.openModal(modal: Modal) => Promise<unknown> Opens a custom modal. Returns a promise resolved with what the modal itself returns calling the resolve() function.

Opens a custom modal. Returns a promise resolved with what the modal itself returns calling the resolve() function.

View on Github
const result = await ctx.openModal({
id: 'regular',
title: 'Custom title!',
width: 'l',
parameters: { foo: 'bar' },
});
if (result) {
ctx.notice(`Success! ${JSON.stringify(result)}`);
} else {
ctx.alert('Closed!');
}
ctx.openConfirm(options: ConfirmOptions) => Promise<unknown> Opens a UI-consistent confirmation dialog. Returns a promise resolved with the value of the choice made by the user.

Opens a UI-consistent confirmation dialog. Returns a promise resolved with the value of the choice made by the user.

View on Github
const result = await ctx.openConfirm({
title: 'Custom title',
content:
'Lorem Ipsum is simply dummy text of the printing and typesetting industry',
choices: [
{
label: 'Positive',
value: 'positive',
intent: 'positive',
},
{
label: 'Negative',
value: 'negative',
intent: 'negative',
},
],
cancel: {
label: 'Cancel',
value: false,
},
});
if (result) {
ctx.notice(`Success! ${result}`);
} else {
ctx.alert('Cancelled!');
}
Entity repos properties
These properties provide access to "entity repos", that is, the collection of resources of a particular type that have been loaded by the CMS up to this moment. The entity repos are objects, indexed by the ID of the entity itself.
ctx.itemTypes: Partial<Record<string, ItemType>> All the models of the current DatoCMS project, indexed by ID.

All the models of the current DatoCMS project, indexed by ID.

View on Github
ctx.fields: Partial<Record<string, Field>> All the fields currently loaded for the current DatoCMS project, indexed by ID. If some fields you need are not present, use the loadItemTypeFields function to load them.

All the fields currently loaded for the current DatoCMS project, indexed by ID. If some fields you need are not present, use the loadItemTypeFields function to load them.

View on Github
ctx.fieldsets: Partial<Record<string, Fieldset>> All the fieldsets currently loaded for the current DatoCMS project, indexed by ID. If some fields you need are not present, use the loadItemTypeFieldsets function to load them.

All the fieldsets currently loaded for the current DatoCMS project, indexed by ID. If some fields you need are not present, use the loadItemTypeFieldsets function to load them.

View on Github
ctx.users: Partial<Record<string, User>> All the regular users currently loaded for the current DatoCMS project, indexed by ID. It will always contain the current user. If some users you need are not present, use the loadUsers function to load them.

All the regular users currently loaded for the current DatoCMS project, indexed by ID. It will always contain the current user. If some users you need are not present, use the loadUsers function to load them.

View on Github
ctx.ssoUsers: Partial<Record<string, SsoUser>> All the SSO users currently loaded for the current DatoCMS project, indexed by ID. It will always contain the current user. If some users you need are not present, use the loadSsoUsers function to load them.

All the SSO users currently loaded for the current DatoCMS project, indexed by ID. It will always contain the current user. If some users you need are not present, use the loadSsoUsers function to load them.

View on Github
Item dialog methods
These methods let you open the standard DatoCMS dialogs needed to interact with records.
ctx.createNewItem(itemTypeId: string) => Promise<Item | null> Opens a dialog for creating a new record. It returns a promise resolved with the newly created record or null if the user closes the dialog without creating anything.

Opens a dialog for creating a new record. It returns a promise resolved with the newly created record or null if the user closes the dialog without creating anything.

View on Github
const itemTypeId = prompt('Please insert a model ID:');
const item = await ctx.createNewItem(itemTypeId);
if (item) {
ctx.notice(`Success! ${item.id}`);
} else {
ctx.alert('Closed!');
}
ctx.selectItem Opens a dialog for selecting one (or multiple) record(s) from a list of existing records of type itemTypeId. It returns a promise resolved with the selected record(s), or null if the user closes the dialog without choosing any record.

Opens a dialog for selecting one (or multiple) record(s) from a list of existing records of type itemTypeId. It returns a promise resolved with the selected record(s), or null if the user closes the dialog without choosing any record.

View on Github
const itemTypeId = prompt('Please insert a model ID:');
const items = await ctx.selectItem(itemTypeId, { multiple: true });
if (items) {
ctx.notice(`Success! ${items.map((i) => i.id).join(', ')}`);
} else {
ctx.alert('Closed!');
}
ctx.editItem(itemId: string) => Promise<Item | null> Opens a dialog for editing an existing record. It returns a promise resolved with the edited record, or null if the user closes the dialog without persisting any change.

Opens a dialog for editing an existing record. It returns a promise resolved with the edited record, or null if the user closes the dialog without persisting any change.

View on Github
const itemId = prompt('Please insert a record ID:');
const item = await ctx.editItem(itemId);
if (item) {
ctx.notice(`Success! ${item.id}`);
} else {
ctx.alert('Closed!');
}
Load data methods
These methods can be used to asyncronously load additional information your plugin needs to work.
ctx.loadItemTypeFields(itemTypeId: string) => Promise<Field[]> Loads all the fields for a specific model (or block). Fields will be returned and will also be available in the the fields property.

Loads all the fields for a specific model (or block). Fields will be returned and will also be available in the the fields property.

View on Github
const itemTypeId = prompt('Please insert a model ID:');
const fields = await ctx.loadItemTypeFields(itemTypeId);
ctx.notice(
`Success! ${fields
.map((field) => field.attributes.api_key)
.join(', ')}`,
);
ctx.loadItemTypeFieldsets(itemTypeId: string) => Promise<Fieldset[]> Loads all the fieldsets for a specific model (or block). Fieldsets will be returned and will also be available in the the fieldsets property.

Loads all the fieldsets for a specific model (or block). Fieldsets will be returned and will also be available in the the fieldsets property.

View on Github
const itemTypeId = prompt('Please insert a model ID:');
const fieldsets = await ctx.loadItemTypeFieldsets(itemTypeId);
ctx.notice(
`Success! ${fieldsets
.map((fieldset) => fieldset.attributes.title)
.join(', ')}`,
);
ctx.loadFieldsUsingPlugin() => Promise<Field[]> Loads all the fields in the project that are currently using the plugin for one of its manual field extensions.

Loads all the fields in the project that are currently using the plugin for one of its manual field extensions.

View on Github
const fields = await ctx.loadFieldsUsingPlugin();
ctx.notice(
`Success! ${fields
.map((field) => field.attributes.api_key)
.join(', ')}`,
);
ctx.loadUsers() => Promise<User[]> Loads all regular users. Users will be returned and will also be available in the the users property.

Loads all regular users. Users will be returned and will also be available in the the users property.

View on Github
const users = await ctx.loadUsers();
ctx.notice(`Success! ${users.map((user) => user.id).join(', ')}`);
ctx.loadSsoUsers() => Promise<SsoUser[]> Loads all SSO users. Users will be returned and will also be available in the the ssoUsers property.

Loads all SSO users. Users will be returned and will also be available in the the ssoUsers property.

View on Github
const users = await ctx.loadSsoUsers();
ctx.notice(`Success! ${users.map((user) => user.id).join(', ')}`);
Navigate methods
These methods can be used to take the user to different pages.
ctx.navigateTo(path: string) => Promise<void> Moves the user to another URL internal to the backend.

Moves the user to another URL internal to the backend.

View on Github
await ctx.navigateTo('/');
Plugin properties
Information about the current plugin. Useful to access the plugin's global configuration object.
ctx.plugin: Plugin The current plugin.

The current plugin.

View on Github
Project properties
ctx.site: Site The current DatoCMS project.

The current DatoCMS project.

View on Github
ctx.environment: string The ID of the current environment.

The ID of the current environment.

View on Github
ctx.isEnvironmentPrimary: boolean Whether the current environment is the primary one.

Whether the current environment is the primary one.

View on Github
ctx.owner: Account | Organization The account/organization that is the project owner.

The account/organization that is the project owner.

View on Github
ctx.ui UI preferences of the current user (right now, only the preferred locale is available).

UI preferences of the current user (right now, only the preferred locale is available).

View on Github
ctx.theme: Theme An object containing the theme colors for the current DatoCMS project.

An object containing the theme colors for the current DatoCMS project.

View on Github
Sizing utilities
A number of methods that you can use to control the size of the plugin frame.
ctx.startAutoResizer() => void Listens for DOM changes and automatically calls setHeight when it detects a change. If you're using datocms-react-ui package, the `` component already takes care of calling this method for you.

Listens for DOM changes and automatically calls setHeight when it detects a change. If you're using datocms-react-ui package, the <Canvas /> component already takes care of calling this method for you.

View on Github
ctx.stopAutoResizer() => void Stops resizing the iframe automatically.

Stops resizing the iframe automatically.

View on Github
ctx.updateHeight(newHeight?: number) => void Triggers a change in the size of the iframe. If you don't explicitely pass a newHeight it will be automatically calculated using the iframe content at the moment.

Triggers a change in the size of the iframe. If you don't explicitely pass a newHeight it will be automatically calculated using the iframe content at the moment.

View on Github
Toast methods
These methods can be used to show UI-consistent toast notifications to the end-user.
ctx.alert(message: string) => Promise<void> Triggers an "error" toast displaying the selected message.

Triggers an "error" toast displaying the selected message.

View on Github
const message = prompt(
'Please insert a message:',
'This is an alert message!',
);
await ctx.alert(message);
ctx.notice(message: string) => Promise<void> Triggers a "success" toast displaying the selected message.

Triggers a "success" toast displaying the selected message.

View on Github
const message = prompt(
'Please insert a message:',
'This is a notice message!',
);
await ctx.notice(message);
ctx.customToast Triggers a custom toast displaying the selected message (and optionally a CTA).

Triggers a custom toast displaying the selected message (and optionally a CTA).

View on Github
const result = await ctx.customToast({
type: 'warning',
message: 'Just a sample warning notification!',
dismissOnPageChange: true,
dismissAfterTimeout: 5000,
cta: {
label: 'Execute call-to-action',
value: 'cta',
},
});
if (result === 'cta') {
ctx.notice(`Clicked CTA!`);
}
Update plugin parameters methods
These methods can be used to update both plugin parameters and manual field extensions configuration.
ctx.updatePluginParameters(params: Record<string, unknown>) => Promise<void> Updates the plugin parameters. Always check ctx.currentRole.meta.final_permissions.can_edit_schema before calling this, as the user might not have the permission to perform the operation.

Updates the plugin parameters.

Always check ctx.currentRole.meta.final_permissions.can_edit_schema before calling this, as the user might not have the permission to perform the operation.

View on Github
await ctx.updatePluginParameters({ debugMode: true });
await ctx.notice('Plugin parameters successfully updated!');
ctx.updateFieldAppearance(...) Performs changes in the appearance of a field. You can install/remove a manual field extension, or tweak their parameters. If multiple changes are passed, they will be applied sequencially. Always check ctx.currentRole.meta.final_permissions.can_edit_schema before calling this, as the user might not have the permission to perform the operation.

Performs changes in the appearance of a field. You can install/remove a manual field extension, or tweak their parameters. If multiple changes are passed, they will be applied sequencially.

Always check ctx.currentRole.meta.final_permissions.can_edit_schema before calling this, as the user might not have the permission to perform the operation.

View on Github
const fields = await ctx.loadFieldsUsingPlugin();
if (fields.length === 0) {
ctx.alert('No field is using this plugin as a manual extension!');
return;
}
for (const field of fields) {
const { appearance } = field.attributes;
const operations = [];
if (appearance.editor === ctx.plugin.id) {
operations.push({
operation: 'updateEditor',
newParameters: {
...appearance.parameters,
foo: 'bar',
},
});
}
appearance.addons.forEach((addon, i) => {
if (addon.id !== ctx.plugin.id) {
return;
}
operations.push({
operation: 'updateAddon',
index: i,
newParameters: { ...addon.parameters, foo: 'bar' },
});
});
await ctx.updateFieldAppearance(field.id, operations);
ctx.notice(`Successfully edited field ${field.attributes.api_key}`);
}
Upload dialog methods
These methods let you open the standard DatoCMS dialogs needed to interact with Media Area assets.
ctx.selectUpload Opens a dialog for selecting one (or multiple) existing asset(s). It returns a promise resolved with the selected asset(s), or null if the user closes the dialog without selecting any upload.

Opens a dialog for selecting one (or multiple) existing asset(s). It returns a promise resolved with the selected asset(s), or null if the user closes the dialog without selecting any upload.

View on Github
const item = await ctx.selectUpload({ multiple: false });
if (item) {
ctx.notice(`Success! ${item.id}`);
} else {
ctx.alert('Closed!');
}
ctx.editUpload(...) Opens a dialog for editing a Media Area asset. It returns a promise resolved with: The updated asset, if the user persists some changes to the asset itself null, if the user closes the dialog without persisting any change An asset structure with an additional deleted property set to true, if the user deletes the asset.

Opens a dialog for editing a Media Area asset. It returns a promise resolved with:

  • The updated asset, if the user persists some changes to the asset itself
  • null, if the user closes the dialog without persisting any change
  • An asset structure with an additional deleted property set to true, if the user deletes the asset.
View on Github
const uploadId = prompt('Please insert an asset ID:');
const item = await ctx.editUpload(uploadId);
if (item) {
ctx.notice(`Success! ${item.id}`);
} else {
ctx.alert('Closed!');
}
ctx.editUploadMetadata(...) Opens a dialog for editing a "single asset" field structure. It returns a promise resolved with the updated structure, or null if the user closes the dialog without persisting any change.

Opens a dialog for editing a "single asset" field structure. It returns a promise resolved with the updated structure, or null if the user closes the dialog without persisting any change.

View on Github
const uploadId = prompt('Please insert an asset ID:');
const result = await ctx.editUploadMetadata({
upload_id: uploadId,
alt: null,
title: null,
custom_data: {},
focal_point: null,
});
if (result) {
ctx.notice(`Success! ${JSON.stringify(result)}`);
} else {
ctx.alert('Closed!');
}