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

Add tree traversal methods to glossary #22

Closed
wooorm opened this issue May 21, 2019 · 0 comments · Fixed by #23
Closed

Add tree traversal methods to glossary #22

wooorm opened this issue May 21, 2019 · 0 comments · Fixed by #23
Labels
📚 area/docs This affects documentation 💪 phase/solved Post is done 🦋 type/enhancement This is great to have

Comments

@wooorm
Copy link
Member

wooorm commented May 21, 2019

Subject of the feature

There are several ways to traverse a tree, typically preorder, postorder, but also inorder and breadth-irst / level-order. See also WikiPedia.

Problem

Projects working with unist typically do this, but either a) don’t document how they do it, or b) document this themselves. Both lead to lacking, incorrect, or incomplete docs.

Expected behaviour

These (most common) types should be documented in the glossary. Maybe with a diagram.

Alternatives

The alternatives (status quo) are shown in problem above.

wooorm added a commit that referenced this issue May 24, 2019
wooorm added a commit that referenced this issue May 25, 2019
Closes GH-22.
Closes GH-23.

Reviewed-by: Christian Murphy <christian.murphy.42@gmail.com>
@wooorm wooorm added ⛵️ status/released 📚 area/docs This affects documentation 🦋 type/enhancement This is great to have labels Aug 12, 2019
@wooorm wooorm added the 💪 phase/solved Post is done label Apr 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
📚 area/docs This affects documentation 💪 phase/solved Post is done 🦋 type/enhancement This is great to have
Development

Successfully merging a pull request may close this issue.

1 participant