Skip to content

Plugin load type too strict for shared type #951

Description

@yuxiaomao

For the moment the plugin system only load a class if Plugin and Main share exactly the same definition for excluded classes.

This isn't pratical for real use cases, where we'd like to build Plugin independent of Main. E.g.

  • add some private variables/function in some class, without the need to rebuild the Plugin;
  • allow h3d.Buffer remains Dynamic in the Plugin but have a driver definition in Main to avoid useless dependencies;
  • do not actually include and try to load all classes if the Plugin does not depend on it

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions