module function · N/workbook
createStyle()
workbook.createStyle(options)
Creates a style.
- Implementation
- Not started
- Design
- Open for proposals suggest how it should read
A
suitescript api
1workbook.createStyle({2 color: /* workbook.Color | string, optional */,3 fontSize: /* workbook.FontSize, optional */,4 fontStyle: /* workbook.FontStyle, optional */,5 fontWeight: /* workbook.FontWeight, optional */,6 textAlign: /* workbook.TextAlign, optional */7});| Parameter | Type | Required | Description |
|---|---|---|---|
| options.color | workbook.Color | string | optional | The font color. |
| options.fontSize | workbook.FontSize | optional | The font size. |
| options.fontStyle | workbook.FontStyle | optional | The font style. |
| options.fontWeight | workbook.FontWeight | optional | The font weight. |
| options.textAlign | workbook.TextAlign | optional | The alignment of text. |
B
mynt syntax
No Mynt syntax yet.
Nothing in the language compiles to workbook.createStyle(options) today. How should it read?
C
community proposals
Competing syntax for createStyle, 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?