v1.2.2

Fixed

• Children inside a parent now render in the same order the database
  returns them. The tree builder used a numeric-aware string comparator
  (localeCompare with numeric: true) which mis-sorted fractional-
  indexing _order keys — e.g. a53 (numerically 53) was placed after
  a5i, while lexicographically a53 < a5i. As a result, dragging a row
  between two siblings could appear to "do nothing" or land the row in
  the wrong slot even though the underlying _order was updated
  correctly.
  The comparator now uses plain lexicographic comparison.