module function · N/format
parse()
format.parse(options)
Takes a formatted value and returns a raw value.
- Implementation
- Not started
- Design
- Open for proposals suggest how it should read
A
suitescript api
1format.parse({2 value: /* string, required */,3 type: /* string, required */,4 value: /* string, required */,5 type: /* string, required */,6 timezone: /* enum, optional */7});
| Parameter | Type | Required | Description |
|---|---|---|---|
| options.value | string | required | The input data to parse. |
| options.type | string | required | The field type (for example, DATE , CURRENCY , INTEGER ). Use the format.Type enum to set this value. |
| options.value | string | required | The string that contains the date and time information in the specified timezone. |
| options.type | string | required | The field type (either DATETIME or DATETIMETZ ). Use the format.Type enum to set this value. |
| options.timezone | enum | optional | The time zone represented by the options.value string. Use the format.Timezone enum to set this value. If a time zone is not specified, the time zone is based on user preference. If the time zone is invalid, the time zone is set to GMT. |
B
mynt syntax
No Mynt syntax yet.
Nothing in the language compiles to format.parse(options) today. How should it read?
C
community proposals
Competing syntax for parse, 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?