Skip to content

Allow Plugins to Extend Known Elements #69

Description

@LeonBein

As a simulation user,
when providing a simulation configuration with plugin-handled elements,
e.g. <catchEvent>.

Expected Behavior
I expect there to be no warning if the element is supported by a plugin
e.g., the EventArrivalRatePlugin.

Actual Behavior
Instead, there is a warning about Element XXX of simulation scenario not supported (see https://github.com/bptlab/scylla/blob/7d1d3039b9cdce6cb6bf35c346830deb4a64b0c1/src/main/java/de/hpi/bpt/scylla/parser/SimulationConfigurationParser.java#L252C63-L252C99).

Proposed solution:
Parser plugins should be allowed to mark elements as known so this defect does not occur anymore.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Topic - PluginsAll issues that belong to plugins, i.e., new ones, improvements, bugs, general plugin handlingTopic - UIAll issues that are related to the user interface of Scylla, especiall GUI improvements and changes.bugenhancement

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions