module function · N/ui/dialog
confirm()
dialog.confirm(options)
Creates a Confirm dialog with OK and Cancel buttons.
- Implementation
- Not started
- Design
- Open for proposals suggest how it should read
A
suitescript api
1dialog.confirm({2 title: /* string, optional */,3 message: /* string, optional */4});
| Parameter | Type | Required | Description |
|---|---|---|---|
| options.title | string | optional | The confirmation dialog title. This value defaults to an empty string. |
| options.message | string | optional | The content of the confirmation dialog. This value defaults to an empty string. |
B
mynt syntax
No Mynt syntax yet.
Nothing in the language compiles to dialog.confirm(options) today. How should it read?
C
community proposals
Competing syntax for confirm, 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?