Skip to content
This repository was archived by the owner on Sep 2, 2021. It is now read-only.
This repository was archived by the owner on Sep 2, 2021. It is now read-only.

Event registry and subclass specification #70

@gdude2002

Description

@gdude2002

So, it's become necessary for plugins to be able to specify event classes when registering their handlers, and to ensure that things are reloadable whilst doing this.

So! We need an event registry. That means a few things.

  • Plugins should never import event classes.
  • Plugins should only refer to events using strings
    • We haven't decided what they'll actually be, but we'll probably change them to class names
  • There will need to be a re-registry when a module is reloaded, so specifying the module and being able to replace the currently registered events for it will be necessary

More news as it happens.

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/8188030-event-registry-and-subclass-specification?utm_campaign=plugin&utm_content=tracker%2F269930&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F269930&utm_medium=issues&utm_source=github).

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions