Last updated
Last updated
This type of extension allows us to retrieve an exportable version of a given meta-model object. Like other extensions, specifications retrieved from this endpoint will enlarge the list of options available on the IDE.
An export extension must be like this:
Where:
extensionType
as these are export extensions this property is export
.
get
a string specifying the way the export content will be obtained (see below).
defaultFilename
(optional) the default file name.
For basic properties refer to .
Lets suppose we want to add a "File out" option to classes and that we count on a URI for that (/classes/{classname}/exports/chunks
for instance).
We could specify our extension like this:
As mentioned above, get
specifies the way the IDE will get the actual contents to be exported. This could be an URI (if it begins with /
) or an attribute of the target element.
In both cases, the value might contain {element.xxx}
expressions, where element
represents the meta-model object for which the export is requested (most likely the object selected in IDE), and xxx
is an valid attribute for such element. This expression will be replaced by the actual value element's attribute.
In the example, assuming the action was triggered from the class MyClass
, the contents will be retrieved from the URI /classes/MyClass/exports/chunks
.
As in the case of get
property, defaultFilename
is a string that can contain zero or more expression of the form {element.xxx}
that will be replaced by their actual value.
In our example, the default file name will be MyClass.ch
.
Assuming the payload of requesting /classes/MyClass/exports/chunks
is the follwing:
A file dialog will be opened and once the user confirms a file name, such contents will be saved.
Valid attributes can be extracted from the corresponding endpoints in the documentation (, , , , ).