Skip to content

Conversation

@paula-stacho
Copy link
Collaborator

@paula-stacho paula-stacho commented Nov 21, 2025

External Links

🎟️

Description

Changes:

  • in addition to the existing onNodeExpandToggle, the client can provide onFieldExpandToggle
  • within the NodeField, the client can provide expanded
  • whether the fields expandable is calculated internally, but the toggle is only displayed if onFieldExpandToggle is provided
  • the top level toggle now has two visuals
  • the top level toggle is not controlled by the client, instead it reacts to the field state and allows expanding if any fields are collapsed
  • [BREAKING CHANGE]: for field-to-field edges, the client is to provide the source|targetFieldId instead of source|targetFieldIndex. the latter isn't suitable anymore because not all fields are visible

Note: Expandability depends on the existence of children more than on the direct types (for example there can be an object without children, or an array/mixed field that does have children).

TODO

  • make sure the height calculation uses the filtered fields

📸 Screenshots/Screencasts

Node with collapse/expand functionality

Screenshot 2025-11-21 at 16 43 34

Node without collapse/expand functionality

Screenshot 2025-11-21 at 16 43 23

Top level and field level collapse behaviour

Screen.Recording.2025-11-20.at.13.52.36.mov

@paula-stacho paula-stacho marked this pull request as ready for review November 21, 2025 15:45
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