You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We'll need to carefully consider how to handle user-ordered lists, especially when multiple templates can apply to a list or leaflist, and those templates may have different or conflicting information about the order of the entries.
I agree we need to be careful, but I think it as a "nice-to-have" capability, in cases where the ordering carries some meaning.
If we allow multiple templates to be applied to a same node, then a priority should be specified with that, as conflict occurs if different templates declares different values for a same node. But I think the user-decided order should always takes the first priority (e.g., the entry marked with position-first should always be the first entry when merging).
No description provided.
The text was updated successfully, but these errors were encountered: