module function · N/translation
selectLocale()
translation.selectLocale(options)
Creates a translation.Handle object in the specified locale from an existing translation.Handle object.
- Implementation
- Not started
- Design
- Open for proposals suggest how it should read
A
suitescript api
1translation.selectLocale({2 handle: /* translation.Handle, required */,3 locale: /* string, required */4});
| Parameter | Type | Required | Description |
|---|---|---|---|
| options.handle | translation.Handle | required | The translation.Handle object to select a locale for. |
| options.locale | string | required | The locale to select. Use the values in the translation.Locale enum to set this value. |
B
mynt syntax
No Mynt syntax yet.
Nothing in the language compiles to translation.selectLocale(options) today. How should it read?
C
community proposals
Competing syntax for selectLocale, 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?