Refactor tentative device registration to use Result type internally #2221
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The tentative device registration uses the flattened success / error enum internally. This causes issues with further changes that we want to make, such as getting rid of internal `trap` calls for the API v2.
frederikrothenberger
deleted the
frederik/refactor-tentative-device-errors
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The tentative device registration uses the flattened success / error enum internally. This causes issues with further changes that we want to make, such as getting rid of internal
trapcalls for the API v2.This is the first part of a bigger refactoring with the goal to remove the
trapcalls fromauthenticated_anchor_operation.