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

Note that leaves must be inline elements #5225

Merged
merged 2 commits into from
Dec 19, 2022

Conversation

SimHoZebs
Copy link
Contributor

Description
Adds a note in the walkthrough section of the documentation that leaves must return inline elements.

Issue
This fixes no existing issues.

Context
One of the things I struggled with in my project was figuring out why arrow navigations between nodes were failing. I soon realized it was because my leaves were described as a div element, not an inline element. Not only did I have no idea where to find information about leaves, but the section itself doesn't seem to document this behavior. I believe this change can at least help prevent the same mistake and give a little more insight as to how and where to find more information regarding leaves.

I also believe updating the Leaves section to include information about this behavior will be great as well. Being new to the repo, I don't understand the logic surrounding leaves enough to contribute to that section.

Checks

  • [ x] The new code matches the existing patterns and styles.
  • [ x] The tests pass with yarn test.
  • [ x] The linter passes with yarn lint. (Fix errors with yarn fix.)
  • [x ] The relevant examples still work. (Run examples with yarn start.)
  • You've added a changeset if changing functionality. (Add one with yarn changeset add.)

I'm not 100% if leaves must be inline elements. That is what I inferred from its behavior. Please let me know if that is not the case.

@changeset-bot
Copy link

changeset-bot bot commented Dec 15, 2022

⚠️ No Changeset found

Latest commit: 0248633

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@dylans dylans merged commit d96887f into ianstormtaylor:main Dec 19, 2022
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