Skip to content

Defining plugins as object bug #2

@abzainuddin

Description

@abzainuddin

When you define plugins as an object, there are some cases which result in some nasty bugs. The problem lies in the fact that the definition is used to store the state of the plugin with isBound.

When multiple view instances are created, the plugins definition object is shared among those view instances. The isBound no longer applies to a single view instance plugin.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions