SecureString object method · N/https
hmac()
SecureString.hmac(options)
Creates an hmac for a https.SecureString .
- Implementation
- Not started
- Design
- Open for proposals suggest how it should read
A
suitescript api
1objSecureString.hmac({2 algorithm: /* string, required */,3 key: /* crypto.SecretKey | https.SecureString, required */4});
| Parameter | Type | Required | Description |
|---|---|---|---|
| options.algorithm | string | required | The hash algorithm. Use values from the https.HashAlg enum. |
| options.key | crypto.SecretKey | https.SecureString | required | A key returned from https.createSecretKey(options) . |
B
mynt syntax
No Mynt syntax yet.
Nothing in the language compiles to SecureString.hmac(options) today. How should it read?
C
community proposals
Competing syntax for hmac, 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?