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

Handling a TraversedPartialPath exception is awkward #108

Open
carver opened this issue Jun 8, 2020 · 0 comments
Open

Handling a TraversedPartialPath exception is awkward #108

carver opened this issue Jun 8, 2020 · 0 comments

Comments

@carver
Copy link
Contributor

carver commented Jun 8, 2020

What was wrong?

In an older HexaryTrieFog API, the TraversedPartialPath exception arguments made more sense. Now, they don't really help you use the fog API without a lot of argument fiddling.

What did you expect it to do?

TPP can return a "simulated" node which helps cleanly deal with the case of using the fog to traverse to a path that doesn't exist anymore.

@carver carver mentioned this issue Jun 8, 2020
2 tasks
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

No branches or pull requests

1 participant