Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Add extra padding to kind and definition nodes #1039

Merged
merged 3 commits into from
Aug 29, 2023

Conversation

georgefst
Copy link
Contributor

@georgefst georgefst commented Aug 24, 2023

The last commit fixes something which would otherwise become a much bigger problem after #1036, since kinds can then be near non-kinds. Although I haven't yet tried combining the changes. It's possible that we would then want to add vertical padding alongside the existing horizontal padding. But this would be trivial to implement now.

These values will be used to affect tree layout, without changing the rendering of individual nodes.

This is essentially a workaround for the Tidy library not having support for per-edge lengths.

Signed-off-by: George Thomas <[email protected]>
This avoids overlaps between highlighted nodes and dashed edges.

Signed-off-by: George Thomas <[email protected]>
This avoids overlaps between siblings.

Signed-off-by: George Thomas <[email protected]>
@georgefst
Copy link
Contributor Author

I dont know why Chromatic isn't showing any changes here. This is precisely the kind of change for which it's supposed to be useful!

@georgefst georgefst marked this pull request as ready for review August 29, 2023 14:19
@georgefst georgefst requested a review from a team August 29, 2023 14:19
@dhess
Copy link
Member

dhess commented Aug 29, 2023

It's possible we've run out of minutes. I switched us back to the free plan a few months ago.

@georgefst georgefst added this pull request to the merge queue Aug 29, 2023
Merged via the queue into main with commit 09c49d9 Aug 29, 2023
@georgefst georgefst deleted the georgefst/node-padding branch August 29, 2023 15:56
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