Skip to content

The sdk does not expose Seeder #59

Description

@SirLouen

Three plugins fill their own schema with demo data and none of them can say so in the contract they are written against.

Current state: pluginkit declares Seeder, and the host calls Seed on every plugin implementing it. The sdk aliases Plugin, Migrator, RouteProvider and PublicPathProvider but not Seeder, so fields, importer and whatsapp each carry a Seed method that satisfies the interface by shape alone, with no sdk level contract to compile against.

Proposal: alias Seeder in the sdk beside the other four, so a plugin author reads one package to learn everything a plugin may implement.

Trigger: fired, three plugins seed and the two plugin rule wanted this at two.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions