module function · N/workbook
createColor()
workbook.createColor(options)
Creates a color.
- Implementation
- Not started
- Design
- Open for proposals suggest how it should read
A
suitescript api
1workbook.createColor({2 alpha: /* number, optional */,3 blue: /* number, optional */,4 green: /* number, optional */,5 red: /* number, optional */6});
| Parameter | Type | Required | Description |
|---|---|---|---|
| options.alpha | number | optional | The alpha portion (opacity or transparency) of the color. |
| options.blue | number | optional | The blue portion of the color. |
| options.green | number | optional | The green portion of the color. |
| options.red | number | optional | The red portion of the color. |
B
mynt syntax
No Mynt syntax yet.
Nothing in the language compiles to workbook.createColor(options) today. How should it read?
C
community proposals
Competing syntax for createColor, 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?