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

decomplect data path and render path #9

Closed
swannodette opened this issue Dec 19, 2013 · 5 comments
Closed

decomplect data path and render path #9

swannodette opened this issue Dec 19, 2013 · 5 comments

Comments

@swannodette
Copy link
Member

Will be important if we want to be able to hint React yet support data joins in Om.

@swannodette
Copy link
Member Author

Doing this would open the door to writing very expressive declarative expressions to compute children - like oh say Datomic style queries :)

@asolove
Copy link

asolove commented Dec 27, 2013

Along these lines, it would be nice if Om's update mechanism were polymorphic on the ICursor instance. The path-based cursors could be one option for meeting the interface, but others are possible.

For example, I have an app where you can select one or more items and then edit their properties. This is currently possible but a bit ugly. I can imagine having my own cursor instance where update would make the same update to multiple places in the state tree.

@swannodette
Copy link
Member Author

Yep been pondering this most of the day #23

@swannodette
Copy link
Member Author

Oops didn't mean to close just comment

@swannodette
Copy link
Member Author

Closing for now, until there's support from React itself, there's nothing much for us to do.

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

No branches or pull requests

2 participants