mynt

module function · N/translation

load()

translation.load(options)

Creates a translation.Handle object with translations for the specified Translation Collections and locales.

Implementation
Not started
Design
Open for proposals suggest how it should read
Proposals
A suitescript api
Signature
translation.load(options)
Returns
translation.Handle
Governance
10 units
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.load({2    collections: /* Object[], required */,3    locales:     /* string[], optional */4});
Oracle reference for this method
ParameterTypeRequiredDescription
options.collectionsObject[]requiredA list of translation.Handle objects to load.
options.collections.aliasstringrequiredAn alias to identify the collection. This alias is used by the script to determine the collection to load.
options.collections.keysstring[]requiredA list of translation keys from the collection to load.
options.localesstring[]optionalA list of locales to load the collection in. 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.load(options) today. How should it read?

C community proposals

Competing syntax for load, 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.load(options)

Suggest syntax for load