mynt

SecureString object method · N/https

appendSecureString()

SecureString.appendSecureString(options)

Appends one https.SecureString to another https.SecureString .

Implementation
Not started
Design
Open for proposals suggest how it should read
Proposals
A suitescript api
Signature
SecureString.appendSecureString(options)
Module
N/https
Returns
https.SecureString
Governance
None
Script types
Server scripts
Version
SuiteScript 2.x, documented for 2.1; since NetSuite 2015.2
call shapefrom Oracle's parameter table
1objSecureString.appendSecureString({2    secureString: /* https.SecureString, required */,3    keepEncoding: /* boolean, optional */4});
Oracle reference for this method
ParameterTypeRequiredDescription
options.secureStringhttps.SecureStringrequiredThe https.SecureString to append.
options.keepEncodingbooleanoptionalKeeps the appended string in its original encoding. Set this value to true to prevent unexpected content re-encoding. The default value is false.
B mynt syntax

No Mynt syntax yet.

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

C community proposals

Competing syntax for appendSecureString, 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/https · SecureString.appendSecureString(options)

Suggest syntax for appendSecureString