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

Interaction with complex state across different adapters is uncomfortable #128

Closed
yuriizinets opened this issue Apr 16, 2022 · 2 comments
Closed
Assignees
Labels
architecture Related to architecture issues

Comments

@yuriizinets
Copy link
Collaborator

In the struct mode it's much easier to initialize nested components and interact with them in next lifecycle steps.
In case of func mode (which is default now) we need to interact with kyoto.Store instance, which is OK for simple state, but interaction with nested components is awful. You need to understand how Core.Component works and use explicit type casting.

Needs to figure out, how to simplify work with components.

@yuriizinets yuriizinets added the architecture Related to architecture issues label Apr 16, 2022
@yuriizinets yuriizinets added this to the v1.1.0 milestone Apr 16, 2022
@yuriizinets yuriizinets self-assigned this Apr 16, 2022
@yuriizinets yuriizinets removed this from the v1.1.0 milestone Apr 19, 2022
@yuriizinets
Copy link
Collaborator Author

It's now possible to use state.New for simple interaction with a state

@yuriizinets
Copy link
Collaborator Author

New architecture will be provided instead of current, not applicable.

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

No branches or pull requests

1 participant