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.

Sign up for GitHub

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

Jump to bottom

Components should not be blueprint types. #138

Closed
iago-lito opened this issue Mar 15, 2024 · 1 comment
Closed

Components should not be blueprint types. #138

iago-lito opened this issue Mar 15, 2024 · 1 comment
Assignees
@iago-lito

Comments

@iago-lito
Copy link
Collaborator

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.
@iago-lito iago-lito self-assigned this Mar 15, 2024
@iago-lito
Copy link
Collaborator Author

Wops, should've been a PR. Sorry for the noise.

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

@iago-lito iago-lito

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@iago-lito