mynt

Signer object method · N/crypto/certificate

update()

Signer.update(options)

Updates the input string to be signed.

Implementation
Not started
Design
Open for proposals suggest how it should read
Proposals
A suitescript api
Signature
Signer.update(options)
Returns
void
Governance
None
Script types
Server scripts
Version
SuiteScript 2.x, documented for 2.1; since NetSuite 2019.1
call shapefrom Oracle's parameter table
1objSigner.update({2    input:         /* string | https.SecureString, required */,3    inputEncoding: /* string, optional */4});
Oracle reference for this method
ParameterTypeRequiredDescription
options.inputstring | https.SecureStringrequiredThe string to update.
options.inputEncodingstringoptionalEncoding of the string to sign (for example, UTF-8, ISO_8859_1, ASCII). The default value is UTF-8. Note: This must be a text value. Values from encode.Encoding ( N/encode Module module) are not accepted.
B mynt syntax

No Mynt syntax yet.

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

C community proposals

Competing syntax for update, 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/crypto/certificate · Signer.update(options)

Suggest syntax for update