mynt

module function · N/translation

get()

translation.get(options)

Creates a translator function for a key in the specified Translation Collection and locale.

Implementation
Not started
Design
Open for proposals suggest how it should read
Proposals
A suitescript api
Signature
translation.get(options)
Returns
translation.Translator
Governance
1 unit
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.get({2    collection: /* string, required */,3    key:        /* string, required */,4    locale:     /* string, optional */5});
Oracle reference for this method
ParameterTypeRequiredDescription
options.collectionstringrequiredThe script ID of the collection.
options.keystringrequiredA valid key from the collection.
options.localestringoptionalA valid locale from the translation.Locale enum. If a locale is not specified, the locale from the current session is used as the default locale.
B mynt syntax

No Mynt syntax yet.

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

C community proposals

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

All discussions

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, 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.get(options)

Suggest syntax for get