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

Components should not be blueprint types. #139

Draft
wants to merge 91 commits into
base: dev
Choose a base branch
from
Draft

Components should not be blueprint types. #139

wants to merge 91 commits into from

Conversation

iago-lito
Copy link
Collaborator

@iago-lito iago-lito commented Mar 15, 2024

Address this design mistake: blueprints and components should be two separate types hierarchies.

Using singleton component instances as ergonomical handles should improve #131.

Take this opportunity to better unify brought blueprint, either implied, embedded or unbrought depending on blueprint value.

This will surface as breaking API changes, but I expect them to remain minor. One major positive change I expect is the simplification of all code within src/components/: this should not become so complex than no one can hack in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant