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: Make limiting depth in traverse() actually work #159

Merged
merged 1 commit into from
Sep 4, 2022

Conversation

asb
Copy link
Contributor

@asb asb commented Sep 2, 2022

Due to a typo (inverted comparison), the test for the traversal depth would always fail. Fix that typo and add test coverage.

Copy link
Collaborator

@pbodnar pbodnar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@asb, great, just 1 little suggestion.

I have just merged the previous PR, so you can also do Git rebase right away.

test/test_traverse.py Show resolved Hide resolved
test/test_traverse.py Outdated Show resolved Hide resolved
Due to a typo (inverted comparison), the test for the traversal depth
would always fail. Fix that typo and add test coverage.
@asb
Copy link
Contributor Author

asb commented Sep 4, 2022

Thanks, typo fixed.

@pbodnar pbodnar merged commit 1980c7d into miyuchina:master Sep 4, 2022
@pbodnar
Copy link
Collaborator

pbodnar commented Sep 4, 2022

Merged, thank you!

@pbodnar pbodnar mentioned this pull request Jan 7, 2023
asb added a commit to muxup/muxup-site that referenced this pull request Feb 27, 2023
…se is fixed

Now my fixes <miyuchina/mistletoe#157>
<miyuchina/mistletoe#158>
<miyuchina/mistletoe#159> are in a released
version, just use the upstream traverse implementation.
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