Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Component Inheritance & Base Context #223

Open
ghostdevv opened this issue Nov 9, 2024 · 0 comments
Open

Component Inheritance & Base Context #223

ghostdevv opened this issue Nov 9, 2024 · 0 comments
Labels
needs shaping More information needed / Decision needs making
Milestone

Comments

@ghostdevv
Copy link
Owner

ghostdevv commented Nov 9, 2024

Having common bases for components may allow us to better organise them. Ideas:

  • InteractionComponent

    This would allow us to extend the defer options, which leads to less duplication. It also might lead perfectly into de-duplicating interactionCreate listeners

  • RunnableComponent

    Standardising around run being the primary handler name allows us to have a shared type. The downside is that it's somewhat redundant since we delegate handling and running to the plugins, also might lead to weird typing.

Somewhat related to RunnableComponent having a common ComponentContext object, and a way of getting it would be ideal for changes to it. This ties in nicely to #225 too

@ghostdevv ghostdevv added the needs shaping More information needed / Decision needs making label Nov 9, 2024
@ghostdevv ghostdevv added this to the v1 milestone Nov 10, 2024
@ghostdevv ghostdevv changed the title Make a InteractionComponent component Component Inheritance Nov 10, 2024
@ghostdevv ghostdevv changed the title Component Inheritance Component Inheritance & Base Context Nov 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs shaping More information needed / Decision needs making
Projects
None yet
Development

No branches or pull requests

1 participant