fix: Principal JSON is compatible with @dfinity/utils jsonReviver helper #770
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.
Description
@peterpeterparker brought up compatibility with
@dfinity/utils
in #766, and I agreed that we should use that standard for more concrete serialization. Instead of the string, will instead return an object,matching a newly exported key,
JSON_KEY_PRINCIPAL
, and a returning a new type,JsonnablePrincipal
.Also extends the
fromText
andfrom
constructors to support strings using the JSON-serialized principalsFixes # (issue)
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration.
Checklist: