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

Data derived key use case #2

Open
bcomnes opened this issue Jul 2, 2019 · 1 comment
Open

Data derived key use case #2

bcomnes opened this issue Jul 2, 2019 · 1 comment

Comments

@bcomnes
Copy link

bcomnes commented Jul 2, 2019

Does this cover the use case of a lists of components that map to a specific data object key?

e.g. React keys use case

Say you have a <ul> full of <li> components. You want to reorder the list and morph the change, the key would determine which component is which during the morphed re-order.

@bcomnes
Copy link
Author

bcomnes commented Jul 2, 2019

Nanomnorph may have this concept built in, but perhaps guard could be a better and more explicit use case for this than overloading the id field.

I need to read the nanomnorph code to see.

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

1 participant