module function · N/plugin
loadImplementation()
plugin.loadImplementation(options)
Instantiates an implementation of the custom plug-in type.
- Implementation
- Not started
- Design
- Open for proposals suggest how it should read
A
suitescript api
1plugin.loadImplementation({2 type: /* string, required */,3 implementation: /* string, optional */4});
| Parameter | Type | Required | Description |
|---|---|---|---|
| options.type | string | required | The script ID of the custom plug-in type. |
| options.implementation | string | optional | The script ID of the custom plug-in implementation. |
B
mynt syntax
No Mynt syntax yet.
Nothing in the language compiles to plugin.loadImplementation(options) today. How should it read?
C
community proposals
Competing syntax for loadImplementation, 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?