module function · N/https/clientCertificate
request()
clientCertificate.request(options)
Sends a SSL secured REQUEST request to a remote server.
- Implementation
- Not started
- Design
- Open for proposals suggest how it should read
A
suitescript api
1clientCertificate.request({2 url: /* string, required */,3 body: /* string, optional */,4 certId: /* string, required */,5 headers: /* object, required */,6 method: /* string, required */7});
| Parameter | Type | Required | Description |
|---|---|---|---|
| options.url | string | required | The URL address of the remote server. |
| options.body | string | optional | The body content to send in the HTTPS request. Only the PUT, POST, and PATCH https.Method values support this parameter; all other methods ignore it. |
| options.certId | string | required | The ID of the client certificate. |
| options.headers | object | required | The HTTP headers associated with the request. |
| options.method | string | required | The HTTP method to be used. Use the https.Method enum to set this value. |
B
mynt syntax
No Mynt syntax yet.
Nothing in the language compiles to clientCertificate.request(options) today. How should it read?
C
community proposals
Competing syntax for request, 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?