Skip to main content

micro-radiant-expanders

4.1.1 (2025-04-18)​

Fixed​

  • Revert change in 3.8.1 that broke identification of options and validations.

4.1.0 (2025-04-15)​

Fixed​

  • Fixed ext harvesting in src/app/model.

Changed​

  • Updated harvest-expanders to 1.0.0. Developers will need to expand before harvesting after upgrading.

4.0.1 (2025-04-14)​

Fixed​

  • Added eager fetching for references to abstract elements. This fixes errors that occur when the target element is not yet loaded and cannot be stubbed.

4.0.0 (2025-04-11)​

Changed​

  • Renamed editor-model-expanders to mr-plugin-expanders Complete artifact is net.democritus.editor:mr-plugin-expanders.

Added​

  • Added Standard Plugin 3 for MR 3 plugins without the NSX configuration.
  • Added tag $mrp.form.select.sorted, which enables sorting for select fields. This tag is enabled in the profile NSX Plugin 3 and Standard Plugin 3.
  • Add custom and feature anchors to the form, tree-node and create-action components.
    • custom-services, custom-variables, custom-constructor and custom-init in several places.
    • submit-before and submit-after in form component.
    • init-model anchor in create-action component.
  • Descriptions in the ElementClass are now used in the form and detail-link components.
  • Added cleanup step to GeneratePluginSkeleton transmuter that removes empty generator logs.

Fixed​

  • Fixed DataParser not loading extensions from children when element itself is not extendable.

3.9.0 (2025-03-31)​

Changed​

  • Improved handling of multi-tiered inheritance.

3.8.1 (2025-03-26)​

Fixed​

  • Fixed dataRegistry synchronisation of elements without explicit identity.

3.8.0 (2025-03-06)​

Added​

  • Added option mrp.tree.reorder to ElementTreeList, which allows the user to reorder items by dragging them.
  • Added support for option mrp.material.symbols.icon to ProjectFacet.
  • Added title field to ProjectViewCategory.

Changed​

  • Views targeted by a ProjectFacet are now expanded.

3.7.2 (2025-02-21)​

Added​

  • Added providers custom anchor to ProjectViewComponentExpander.

3.7.1 (2025-02-18)​

Changed​

  • Updated plugin project glint version to include patches shipped in MR 3.0.
  • Changed maven dependency:unpack markers directory to target/mr-plugin-markers.

Fixed​

  • Fixed extensions not being added correctly in the DataParser.

3.7.0 (2025-01-31)​

Changed​

Prime Radiant currently does not support target micro-radiant versions with more than 1 version number. So, instead of version 2.2.0, the next version will be 3.0.0.

  • Profile NSX Plugin 3 replaces NSX Plugin 2.2.
  • Target mr version has been changed to 3.
  • Some tags have been renamed
    • #mrp.microradiant.2.0 => #mrp.microradiant.v2
    • #mrp.microradiant.2.2 => #mrp.microradiant.v3

3.6.0 (2025-01-30)​

Added​

  • Added new tag #mrp.update.selective, which expands a list of properties in each detail component. When updating an element, only properties listed here will be updated. This significantly reduces the size of some update calls, but the list might need to be modified when adding customizations.
  • Added profile NSX Plugin 2.2, which creates plugins for Micro-Radiant 2.2.x.
    • This profile enables material symbols by default. Icons can be set with the option mrp.material.symbols.icon
    • Dependencies will be updated to match the versions in MR 2.2.
    • This profile also enables the #mrp.update.selective tag by default, so be careful when updating!

3.5.0 (2025-01-24)​

Changed​

  • Introduced 2 separate tags for the #mrp.nsx tag:
    • #mrp.project.nsx adds the NSX parent to the pom.xml.
    • #mrp.npmrc.nsx adds an .npmrc file, which is no longer recommended.
  • Introduced a tag #mrp.project.yarn, which adds configuration for using the yarn package manager.
  • Added NSX Plugin Yarn and NSX RnD Plugin Yarn profiles.

3.4.0 (2025-01-21)​

Added​

  • Added activation element, which can be used to define when an extension should be activated.

Changed​

  • Refactor GeneratePluginSkeleton transmuter to fix a number of issues where it would duplicate DetailComponents, or generate an incorrect model for extension references.

Fixed​

  • Fixed issue with abstract extensions adding too many context menu actions.

3.3.0 (2025-01-09)​

Changed​

  • Added mechanism in local plugin deployment to wait until model server is ready.

Fixed​

  • Fixed extensions loaded from child composites to be returned by the DataParser.
  • Added workaround for bad handling of version conflicts in native federation. This should fix issues encountered when using a different glint version.

3.2.2 (2024-12-18)​

Fixed​

  • Fixed bug causing a large number of requests to be sent.

3.2.1 (2024-12-18)​

Fixed​

  • Fixed issue where target of actions were not set in the context-actions Components.

3.2.0 (2024-12-18)​

Changed​

  • Context-actions Components now use the ACTIONS token directly instead of passing through the ModelActionsService. This fixes issues experienced by plugins with extensions, where the ModelSelectionService was not provided when the CreateAction for the extension was initialized.
  • Versions in package.json are now set to specific versions to ensure runtime compatibility with the micro-radiant.
  • Changed default icon for CreateAction to fa-plus

3.1.0 (2024-12-12)​

Changed​

  • Added logic to DataParser to re-fetch instance if the format does not match the expected profile
  • Changed start-model-server script to use version of option when downloading the model server jar

3.0.0 (2024-12-04)​

Changed​

  • Updated glint to 2.0.0. This version introduces changes to the plugin loading mechanism. Plugins now have a plugin module that lists the content of the plugin.
  • Changed setup to use native federation. NOTE: Due to an issue in the module federation library, the build can hang when it fails. Add a timeout to the Jenkinsfile of the plugin to prevent it from running indefinitely.
  • TreeToModel classes now look up instances in the DataRegistry to update existing Models if there are any.
  • Changed DiagramComponents to have a more predictable model.

Added​

  • Added PluginDependency element. These can be added to the EditorPlugin model to install another plugin for testing. These plugins are automatically downloaded during expansion.
  • Added EditorTask element. This element generates a service that runs during the plugin startup mechanism.
  • Added ProjectFacet element, which can represent a program in the project navigation or adds a separate view.

2.8.1 (2024-11-19)​

Changed​

  • Changed NsxNpmrcExpander so that it only adds the fortawesome repository for plugins with fa-pro.

2.8.0 (2024-10-22)​

Added​

  • Added .cleanExclude Expander that excludes node_modules and mr-plugins directory for expansion cleanup. Requires expanders-maven-plugin:2024.5.0 or higher and at least one expansion with teh new version to work.
  • Added NSX Plugin profile, which includes setup for NSX projects, but does not enable fontawesome pro.
  • Added option mrp.requirements.nsModelServer.version for EditorPlugin. Use this to define a minimum ns-model-server version for a plugin. If the micro-radiant has an outdated ns-model-server, it will be updated to fit this minimum version when the plugin is installed.

2.7.0 (2024-10-11)​

Added​

  • Added README file to expanded plugin project.

Changed​

  • npm start now deploys to 16001 be default, configurable with the option mrp.demo.port.

Fixed​

  • Fixed error occurring on tree nodes without content which are open by default. (e.g. Programs without composite children)

2.6.0 (2024-10-02)​

Added​

  • Added support for model remarks to tree node labels.

2.5.0 (2024-09-30)​

Added​

  • Added fields to Plugin model for deploying the plugin.
  • Added pom.xml Expander for packaging plugins.
  • Added #mrp.nsx profile tag to nsx specific deployment configuration.
  • Added DeleteAction element.

Changed​

  • Changed how ontologies are linked in the Plugin model. Ontologies are now grouped under EditorMetamodels,
    which can have a type to label them as source or dependency.
  • Removed some unused element classes.
  • TreeNode Components now use modelPropertySignal to represent tree lists to improve syncing after changes.

Fixed​

  • Extension names can now contain dashes.
  • Fixed issue with harvest in model directories by adding .harvestInclude files in those directories.

2.4.1 (2024-09-06)​

Fixed​

  • Updated metamodel expanders to fix issue with ref attribute on action in XML not being parsed correctly.

2.4.0 (2024-09-06)​

Added​

  • Added context-menu to tree-extension component.
  • Added diagram components and registration for these in plugin service.
  • Added option mrp.tree.open to open a tree node by default.
  • Added option mrp.tree.group.skip to omit the group node for a composition and show as direct children of the parent node.
  • Added option fontawesome.variant (pro, free) on editorPlugin to pick the right licence.
  • Added filter field to tree view panel header.

Changed​

  • Changed 'ImportedOntology' module type to 'OntologyImport' to prevent model loading issues.
  • Changed project structure. The expanders now expand an entire plugin project with configuration files.
  • ElementTreeList now borrows the icon of the childNodeType if it does not define the option itself.

Fixed​

  • Fixed calls to foreign constructors to be replaced with a factory method.
  • Fixed options, extensions and metadata missing from TYPE interfaces.

2.3.0 (2024-07-02)​

Added​

  • Added support for model extensions.

Changed​

  • Changed profiles so it works better with abstract ElementClasses
  • TreeNode Context menus are now expanded as a separate component.

2.2.4 (2024-06-27)​

Fixed​

  • Fixed a compile issue for prime-plugin. Root tag #mrp.elements.included is use to enable the direct use of OptionModel and MetadataModel.

2.2.3 (2024-06-26)​

Fixed​

  • Fixed _type value for new options.

2.2.2 (2024-06-26)​

Fixed​

  • Fixed compile issues for plugin depending on external ontologies.

2.2.1 (2024-06-24)​

Fixed​

  • Fixed issue where an empty context menu would be added if no actions are defined in a tree-node child.

2.2.0 (2024-03-21)​

Changed​

  • Replaced identity and instanceLabel properties with _id and _instanceLabel

2.1.0 (2024-03-19)​

Changed​

  • Implement changes for glint 1.2.0

2.0.0 (2023-12-01)​

Moved expanders from micro-radiant repository.

Changed​

Expanders are now based on a metamodel describing the Components.

Every plugin has a plugin.xml file, in a model directory. It references the ontologies on which the plugin is based.


<editorPlugin name="prime">
  <metamodels>
    <editorMetamodel>
      <ontology name="elements"/>
    </editorMetamodel>
    <editorMetamodel>
      <ontology name="expansionControl"/>
    </editorMetamodel>
  </metamodels>
</editorPlugin>

The expansionSettings should target editorElements::EditorPlugin:


<expansions>
  <expansion>
    <type component="editorElements" name="EditorPlugin"/>
    <target>plugin</target>
  </expansion>
</expansions>

The model can then be initialized with the GeneratePluginSkeleton transmuter.