module function · N/https
request()
https.request(options)
Sends an HTTPS request and returns the response.
- Implementation
- Not started
- Design
- Open for proposals suggest how it should read
A
suitescript api
1https.request({2 method: /* enum, required */,3 url: /* string, required */,4 body: /* string | Object, optional */,5 credentials: /* string[], optional */,6 headers: /* Object, optional */7});| Parameter | Type | Required | Description |
|---|---|---|---|
| options.method | enum | required | The HTTPS request method. Use https.Method to set this value. |
| options.url | string | required | The HTTPS URL being requested. |
| options.body | string | Object | 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.credentials | string[] | optional | An array of string GUIDs. These GUIDS are searched for in the options.body of the request and are replaced by the decrypted passwords before they are sent to a third-party server. |
| options.headers | Object | optional | The HTTPS headers. For more information, see HTTPS Header Information . |
B
mynt syntax
No Mynt syntax yet.
Nothing in the language compiles to https.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?