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
Proposals
A
Signature
translation.selectLocale(options)
Returns
translation.Handle
Governance
None
Script types
Client and server scripts
Version
SuiteScript 2.x, documented for 2.1; since NetSuite 2019.1
call shapefrom Oracle's parameter table
1translation.selectLocale({2    handle: /* translation.Handle, required */,3    locale: /* string, required */4});
Oracle reference for this method
ParameterTypeRequiredDescription
options.handletranslation.HandlerequiredThe translation.Handle object to select a locale for.
options.localestringrequiredThe locale to select. Use the values in the translation.Locale enum to set this value.
B

No Mynt syntax yet.

Nothing in the language compiles to translation.selectLocale(options) today. How should it read?

C

Competing syntax for selectLocale, from GitHub Discussions. Select two or more to compare them side by side.

All discussions

Loading proposals from GitHub…

D

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, save and Ref[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?

N/translation · translation.selectLocale(options)

Suggest syntax for selectLocale