Document object method · N/xml
importNode()
Document.importNode(options)
Imports a node from another document to this document.
- Implementation
- Not started
- Design
- Open for proposals suggest how it should read
A
suitescript api
1objDocument.importNode({2 importedNode: /* xml.Node, required */,3 deep: /* boolean, required */4});
| Parameter | Type | Required | Description |
|---|---|---|---|
| options.importedNode | xml.Node | required | Node from another XML document to import. |
| options.deep | boolean | required | Use true to import the node, its attributes, and all descendents. Use false to only import the node and its attributes. Important: This parameter is not supported on Internet Explorer. |
B
mynt syntax
No Mynt syntax yet.
Nothing in the language compiles to Document.importNode(options) today. How should it read?
C
community proposals
Competing syntax for importNode, 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?