Skip to content

feature: extension options #11

Description

@bdbch

What feature do you want?

Right now inksane extensions don't take options so once an extension is created, it can't be configured from the outside. This sucks if you want to allow users to configure specific parts of your extension.

How should it work?

When a user creates an extension - instead of just creating a flat object, it should be a class instance of an Extension class which can store options on itself - and when configured creates a clone of itself with the new configuration set created by the user.

Which use cases will it handle?

This allows extension developers (but also our core extensions) to take options and change default behavior.

How urgent is it for you?

Blocks my adoption or current work

Code of Conduct

  • I agree to follow this project's Code of Conduct.

Activity

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

Metadata

Metadata

Assignees

Labels

status: needs triageNew report not yet confirmed or categorizedtype: featureNew editor capability or extension

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions