2.3.7-alpha.0

Features

• Make drop target depth in last-of-subtree locations dependent on x-coordinates of the mouse, allowing the user to
  drop in higher depths than the currently hovering item. This behavior is automatically used if renderDepthOffset
  on the renderers is set to a non-zero value. (#148)
  • This also applies when dropping at the top of an item where the item prior is of deeper depth, meaning that
    in this case the decision of dropping into the container above or directly above the hovering item will depend
    on the x-coordinate of the mouse.
• Add setDomFocus argument to focus-item methods to provide an escape hatch to set the focus state of an item in RCT
  without updating the DOM focus. This defaults to true in all existing methods to maintain the current behavior if
  it is absent. (#336)
• Allow customizing when a subtree is rendered or not with the new shouldRenderChildren prop. This can be used to
  create opening and closing animations on subtrees. See Demo
  and Demo Implementation for details. (#333)

Bug Fixes

• Fix a bug where the parentId property in the renderItemsContainer render method was incorrectly set to the tree id
  for the root container.

2.3.6

Other Changes

• Add funding link to package.json

2.3.5-alpha.0

Features

• Make drop target depth in last-of-subtree locations dependent on x-coordinates of the mouse, allowing the user to
  drop in higher depths than the currently hovering item. This behavior is automatically used if renderDepthOffset
  on the renderers is set to a non-zero value. (#148)
• Add setDomFocus argument to focus-item methods to provide an escape hatch to set the focus state of an item in RCT
  without updating the DOM focus. This defaults to true in all existing methods to maintain the current behavior if
  it is absent. (#336)
• Allow customizing when a subtree is rendered or not with the new shouldRenderChildren prop. This can be used to
  create opening and closing animations on subtrees. See Demo
  and Demo Implementation for details. (#333)

Bug Fixes

• Fix a bug where the parentId property in the renderItemsContainer render method was incorrectly set to the tree id
  for the root container.

2.3.5

Features

• Add setDomFocus argument to focus-item methods to provide an escape hatch to set the focus state of an item in RCT
  without updating the DOM focus. This defaults to true in all existing methods to maintain the current behavior if
  it is absent. (#336)
• Allow customizing when a subtree is rendered or not with the new shouldRenderChildren prop. This can be used to
  create opening and closing animations on subtrees. See Demo
  and Demo Implementation for details. (#333)

Bug Fixes

• Fix a bug where the parentId property in the renderItemsContainer render method was incorrectly set to the tree id
  for the root container.

2.3.4

Other Changes

• Make the onDidChangeTreeDataEmitter prop on a static data provider public

2.3.3

Bug Fixes and Improvements

• Maintain original item order when dropping items (#315)
• Expose some hooks and internally used components in the public API that were hidden before (#313)

2.3.2

Bug Fixes and Improvements

• Improved the implementation of the onSelectItems prop to not run during a React update, which was causing issues
  in some cases (#278)

2.3.1

Bug Fixes

• Items dropped at the bottom most position (outside of the rectangle of tree items, but still inside the tree container)
  will now be placed in the root item, at the final position, instead of the contents of the last open item (#261)

2.2.5-alpha.0

Breaking Changes

• Changed the behavior for dropping an item at the bottom of an open folder has changed, and will now drop
  into the open folder at its top, instead of the parent folder below the open folder. See discussion at #148 for details.
  You can opt out of this behavior by setting the canDropBelowOpenFolders prop on the tree environment (#148).

Bug Fixes

• Fixed a bug where the canRename property in a tree item payload was not respected.

2.3.0

Breaking Changes

• Changed the behavior for dropping an item at the bottom of an open folder has changed, and will now drop
  into the open folder at its top, instead of the parent folder below the open folder. See discussion at #148 for details.
  You can opt out of this behavior by setting the canDropBelowOpenFolders prop on the tree environment (#148).

Bug Fixes

• Fixed a bug where the canRename property in a tree item payload was not respected.