module function · N/ui/dialog
create()
dialog.create(options)
Creates a dialog with specified buttons.
- Implementation
- Not started
- Design
- Open for proposals suggest how it should read
A
suitescript api
1dialog.create({2 buttons: /* string[], optional */,3 title: /* string, optional */,4 message: /* string, optional */5});
| Parameter | Type | Required | Description |
|---|---|---|---|
| options.buttons | string[] | optional | A list of buttons to include in the dialog. Each item in the button list must be a Javascript Object that contains a label and a value property. By default, a single button with the label OK and the value true is used. |
| options.title | string | optional | The dialog title. This value defaults to an empty string. |
| options.message | string | optional | The content of the dialog. This value defaults to an empty string. |
B
mynt syntax
No Mynt syntax yet.
Nothing in the language compiles to dialog.create(options) today. How should it read?
C
community proposals
Competing syntax for create, from GitHub Discussions. Select two or more to compare them side by side.
Loading proposals from GitHub…
D
suggest an alternative
Write the Mynt you wish you could write.
A good proposal shows the syntax, the SuiteScript it should become, and argues for it: why it is clearer, how it fits the rest of the language, what it makes harder.
- Clarity. Does it say what happens, without ceremony?
- Consistency. Does it read like
load,saveandRef[field]? - Expressiveness. Does it cover the cases people actually write?
- Honesty. Does it hide a NetSuite cost, such as governance, that a reader should see?