-
Notifications
You must be signed in to change notification settings - Fork 319
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
Sort order? #10
Comments
+1. Would be great to have them sorted according a given criteria. |
Ok good. We don't have any sorting at the moment but we will add this for the next version of document. Thanks for this good recommendation. |
Also we could filter it, not only sort it :) |
And also categorize them? |
So I think we should have an advanced grid for doing filtering, sorting and categorizing. |
+1 Please filter them alphabetically by default. |
+1 As the list grows, it would be really handy to be able to filter and sort them by the various features. |
+1, absolutely agree with opener) |
Still no indication of what the list order means, or any way of sorting the list. However, the list is filterable (by the text in the descriptions), which is a nice improvement. So, I guess I'll leave the issue open. 😈 |
Hey yeah sorry, been a bit swamped lately.
1. Lists can be reordered by providing them with a unique ID (e.g. an
actual id property). This is similar to how react handles sibling
reordering with their "key" property.
2. By setting an ".isSameNode()" method on any element, the diffing
algorithm will compare the new node with the old node to determine if it
has changed or not. This is analogous to Reacts "shouldComponentUpdate"
lifecycle event.
I think most diffing libs rely on similar methods to reduce the amount of
work they need to do on every cycle. I hope this explains how to do it for
morphdom / choo too. Thanks! 🍕
…On Fri, Feb 24, 2017, 03:00 Michael R. Bernstein ***@***.***> wrote:
Still no indication of what the list order means, or any way of sorting
the list.
However, the list is filterable (by the text in the descriptions), which
is a nice improvement.
So, I guess I'll leave the issue open. 😈
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#10 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACWleocdobf5k6qdII5C4bPBrWipb67jks5rfjnOgaJpZM4AdCwe>
.
|
It is unclear what the sort order of the frameworks is. Is it some measure of popularity? Making this explicit would be helpful.
The text was updated successfully, but these errors were encountered: