Skip to content

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Jan 2, 2023

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

d3-state-visualizer@2.0.0

Major Changes

  • b323f77: Upgrade D3

    • Remove UMD build.
    • Split style option into chartStyles, nodeStyleOptions, textStyleOptions, and linkStyles.
    • The shape of the argument passed to the onClickText option has been updated.
    • Rename InputOptions to Options, Primitive to StyleValue, and NodeWithId to HierarchyPointNode<Node>.

Patch Changes

  • Updated dependencies [b323f77]
  • Updated dependencies [b323f77]
    • d3tooltip@3.0.0
    • map2tree@3.0.0

d3tooltip@3.0.0

Major Changes

  • b323f77: Upgrade D3

    • Remove UMD build.
    • Upgrade d3 peer dependency from v3 to v7.
    • Remove attr configuration method.
    • Rename style configuration method to styles and move to options.
    • Move text configuration method to options.
    • Remove d3 parameter as first parameter for tooltip.

map2tree@3.0.0

Major Changes

@redux-devtools/chart-monitor@4.0.0

Major Changes

  • b323f77: Upgrade D3

    • Split style option into chartStyles, nodeStyleOptions, textStyleOptions, and linkStyles.
    • The shape of the argument passed to the onClickText option has been updated.

Patch Changes

  • Updated dependencies [b323f77]
    • d3-state-visualizer@2.0.0

react-json-tree@0.18.0

Minor Changes

  • 81926f3: Remove UNSAFE method from react-json-tree

    • Replace shouldExpandNode with shouldExpandNodeInitially. This function is now only called when a node in the tree is first rendered, when before it would update the expanded state of the node if the results of calling shouldExpandNode changed between renders. There is no way to replicate the old behavior exactly, but the new behavior is the intended behavior for the use cases within Redux DevTools. Please open an issue if you need a way to programatically control the expanded state of nodes.
    • Bump the minimum React version from 16.3.0 to 16.8.0 so that react-json-tree can use hooks.
    • Tightened TypeScript prop types to use unknown instead of any where possible and make the key path array readonly.

@redux-devtools/app@2.2.1

Patch Changes

  • Updated dependencies [b323f77]
  • Updated dependencies [b323f77]
    • d3-state-visualizer@2.0.0
    • @redux-devtools/chart-monitor@4.0.0
    • @redux-devtools/inspector-monitor@3.0.2
    • @redux-devtools/log-monitor@4.0.2
    • @redux-devtools/rtk-query-monitor@3.1.1

@redux-devtools/inspector-monitor@3.0.2

Patch Changes

  • Updated dependencies [81926f3]
    • react-json-tree@0.18.0

@redux-devtools/log-monitor@4.0.2

Patch Changes

  • Updated dependencies [81926f3]
    • react-json-tree@0.18.0

@redux-devtools/rtk-query-monitor@3.1.1

Patch Changes

  • Updated dependencies [81926f3]
    • react-json-tree@0.18.0

remotedev-redux-devtools-extension@3.0.18

Patch Changes

  • Updated dependencies [81926f3]
    • react-json-tree@0.18.0
    • @redux-devtools/app@2.2.1

d3-state-visualizer-tree-example@0.1.5

Patch Changes

  • Updated dependencies [b323f77]
  • Updated dependencies [b323f77]
    • d3-state-visualizer@2.0.0
    • map2tree@3.0.0

react-json-tree-example@1.1.8

Patch Changes

  • Updated dependencies [81926f3]
    • react-json-tree@0.18.0

@github-actions github-actions bot force-pushed the changeset-release/main branch 7 times, most recently from d03200f to a6aed20 Compare January 5, 2023 13:51
@github-actions github-actions bot force-pushed the changeset-release/main branch from a6aed20 to 1069abb Compare January 5, 2023 14:01
@Methuselah96 Methuselah96 enabled auto-merge (squash) January 5, 2023 14:05
@Methuselah96 Methuselah96 merged commit fa25234 into main Jan 5, 2023
@Methuselah96 Methuselah96 deleted the changeset-release/main branch January 5, 2023 14:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants