module function · N/crypto
createCipher()
crypto.createCipher(options)
Creates and returns a new crypto.Cipher Object.
- Implementation
- Not started
- Design
- Open for proposals suggest how it should read
A
suitescript api
1crypto.createCipher({2 algorithm: /* string, required */,3 key: /* object, required */,4 padding: /* string, optional */5});| Parameter | Type | Required | Description |
|---|---|---|---|
| options.algorithm | string | required | The encryption algorithm. Use the crypto.EncryptionAlg enum to set the value. |
| options.key | object | required | The crypto.SecretKey object. Note: When using the crypto.SecretKey object for an AES algorithm, the length of the text (secret key) that is used to generate the GUID must be 16, 24, or 32 characters. |
| options.padding | string | optional | The padding for the cipher text. Use the crypto.Padding enum to set the value. The default value is crypto.Padding.PKCS5Padding . |
B
mynt syntax
No Mynt syntax yet.
Nothing in the language compiles to crypto.createCipher(options) today. How should it read?
C
community proposals
Competing syntax for createCipher, from GitHub Discussions. Select two or more to compare them side by side.
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,saveandRef[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?