mynt

module function · N/https

createSecureString()

https.createSecureString(options)

Creates an https.SecureString Object.

Implementation
Not started
Design
Open for proposals suggest how it should read
Proposals
A suitescript api
Signature
https.createSecureString(options)
Module
N/https
Returns
Object
Governance
None
Script types
Server scripts
Version
SuiteScript 2.x, documented for 2.1; since NetSuite 2015.2
call shapefrom Oracle's parameter table
1https.createSecureString({2    input: /* string, required */3});
Oracle reference for this method
ParameterTypeRequiredDescription
options.inputstringrequiredThe string to convert to a https.SecureString . The following patterns are accepted: \{[a-fA-F0-9]{32}\} or alternatively { + <32 hexadecimal characters forming a UUID/GUID> + } \{custsecret[a-zA-Z0-9_]{1,89}\} or alternatively { + custsecret + <1 up to 89 alfanumeric characters or underscores > + } specific payment-plug-in tokens
B mynt syntax

No Mynt syntax yet.

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

C community proposals

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

Suggest syntax for createSecureString