module function · N/ui/message
create()
message.create(options)
Creates a message that can be displayed or hidden near the top of the page.
- Implementation
- Not started
- Design
- Open for proposals suggest how it should read
A
suitescript api
1message.create({2 type: /* message.Type, required */,3 title: /* string, optional */,4 message: /* string, optional */,5 duration: /* int | string, optional */6});
| Parameter | Type | Required | Description |
|---|---|---|---|
| options.type | message.Type | required | The type of message to create. Set this value using the message.Type enum. |
| options.title | string | optional | The message title. This value defaults to an empty string. |
| options.message | string | optional | The content of the message. This value defaults to an empty string. |
| options.duration | int | string | optional | The amount of time, in milliseconds, to show the message. The default is 0, which shows the message until Message.hide() Message.hide() is called. If you use a string, it will be parsed to a number. If you specify a duration both when you create the message and when you show it using Message.show(options) , the value when you show it takes precedence. |
B
mynt syntax
No Mynt syntax yet.
Nothing in the language compiles to message.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?