mynt

MessageData object method · N/pgp

encrypt()

MessageData.encrypt(options)

Creates a message that is encrypted and optionally signed.

Implementation
Not started
Design
Open for proposals suggest how it should read
Proposals
A suitescript api
Signature
MessageData.encrypt(options)
Module
N/pgp
Returns
pgp.Message
Governance
None
Script types
Server scripts
Version
SuiteScript 2.x, documented for 2.1; since NetSuite 2022.2
call shapefrom Oracle's parameter table
1objMessageData.encrypt({2    signingKeys: /* pgp.Key | pgp.Key [], optional */3});
Oracle reference for this method
ParameterTypeRequiredDescription
options.signingKeyspgp.Key | pgp.Key []optionalZero or more keys used for signing. If a key contains multiple valid signing (sub)keys, the most recent key added will be used. Default value = [] .
B mynt syntax

No Mynt syntax yet.

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

C community proposals

Competing syntax for encrypt, 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/pgp · MessageData.encrypt(options)

Suggest syntax for encrypt