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
Copy file name to clipboardExpand all lines: packages/docs/docs/changelog.mdx
+5-19
Original file line number
Diff line number
Diff line change
@@ -4,27 +4,13 @@ sidebar_position: 6
4
4
5
5
# Changelog
6
6
7
-
## 2.3.7-alpha.0 - 10/03/2024
7
+
## 2.3.7 - 15/03/2024
8
8
9
-
### Features
10
-
11
-
- Make drop target depth in last-of-subtree locations dependent on x-coordinates of the mouse, allowing the user to
12
-
drop in higher depths than the currently hovering item. This behavior is automatically used if `renderDepthOffset`
13
-
on the renderers is set to a non-zero value. (#148)
14
-
- This also applies when dropping at the top of an item where the item prior is of deeper depth, meaning that
15
-
in this case the decision of dropping into the container above or directly above the hovering item will depend
16
-
on the x-coordinate of the mouse.
17
-
- Add `setDomFocus` argument to focus-item methods to provide an escape hatch to set the focus state of an item in RCT
18
-
without updating the DOM focus. This defaults to true in all existing methods to maintain the current behavior if
19
-
it is absent. (#336)
20
-
- Allow customizing when a subtree is rendered or not with the new `shouldRenderChildren` prop. This can be used to
21
-
create opening and closing animations on subtrees. See [Demo](https://rct.lukasbach.com/storybook/?path=/story/core-basic-examples--animated-expanding-and-collapsing)
22
-
and [Demo Implementation](https://github.com/lukasbach/react-complex-tree/blob/main/packages/core/src/stories/BasicExamples.stories.tsx#L561) for details. (#333)
23
-
24
-
### Bug Fixes
9
+
# Featureset revertion to the state of 2.3.6
25
10
26
-
- Fix a bug where the `parentId` property in the `renderItemsContainer` render method was incorrectly set to the tree id
27
-
for the root container.
11
+
I've noticed that I've accidentally been pushing a few experimental releases that were meant to be released
12
+
as prerelease under the "Latest" tag in NPM. This reverts the latest release to the state of 2.3.6, the last
13
+
proper "latest" release. Prereleases will from now on be released under the "prerelease" tag in NPM.
0 commit comments