A tree-based editor for EMF model instances in VS Code. It opens .xmi, .json and .ecore
files and edits them reflectively, so it works for generated metamodels as well as for metamodels
that are only available as a .ecore file.
This extension is a preview. File formats and behavior may still change before 1.0.
Features
Tree and properties view. The left pane shows the containment tree, the right pane the
attributes and references of the selected object.
Editing. Attributes are edited with a text field, number field, checkbox or enum drop-down,
depending on their type. Containment features get + Add with a choice of the concrete
subclasses; references get + Link for objects in the same file and Link external… for
objects in other files.
Follow reference. Jumps to the referenced object in the tree.
New model instance. The command TypeMF: New Model Instance creates a new file with a
root object of a class you pick, either from a registered metamodel or from a .ecore file. The
new file can be saved as XMI, JSON or Ecore.
Missing metamodels. When a file uses a metamodel that isn't registered, the editor asks you
to select the .ecore file(s) for it.
Opening files
.ecore files open in this editor by default. For .xmi and .json files, use
Open With… → TypeMF Instance Editor, so that ordinary JSON files keep opening in the text
editor.
Registering metamodels
The editor finds metamodels in the shared registry of the
TypeMF Runtime
extension, which is installed with it. A metamodel gets there in one of two ways:
an extension provides a generated model package (see @typemf/vscode-runtime on npm), or
the typemf.ecoreMappings setting maps an nsURI to a .ecore file in your workspace:
