mynt

module function · N/pgp

createMessageData()

pgp.createMessageData(options)

Creates new message data.

Implementation
Not started
Design
Open for proposals suggest how it should read
Proposals
A suitescript api
Signature
pgp.createMessageData(options)
Module
N/pgp
Returns
pgp.MessageData
Governance
None
Script types
Server scripts
Version
SuiteScript 2.x, documented for 2.1; since NetSuite 2022.2
call shapefrom Oracle's parameter table
1pgp.createMessageData({2    content:  /* string, required */,3    filename: /* string, optional */,4    date:     /* Date object, optional */,5    format:   /* pgp.Format, optional */6});
Oracle reference for this method
ParameterTypeRequiredDescription
options.contentstringrequiredContent of the message.
options.filenamestringoptionalFile name if the message represents a file, empty string otherwise.
options.dateDate objectoptionalDate of the message or modification date of the file. Default value = new Date() .
options.formatpgp.FormatoptionalLiteral data packet type. Default value = Format.UTF8 , if content is a string. Format.BINARY otherwise.
B mynt syntax

No Mynt syntax yet.

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

C community proposals

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

Suggest syntax for createMessageData