[CC-3759] Change Keypair properties from private to protected#234
Merged
Conversation
…le JSON serialization via expose(). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…led property visibility - Change `detailed` to private since it is a fetch-control flag and must not be serialized - Add unit test verifying expose() includes all protected properties with correct values and excludes privateKey and detailed - Add integration test verifying expose() reflects fetched keypair data including nested payment type objects Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Ryouzanpaku
changed the title
sixer1182
approved these changes
Jun 22, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Keypairfromprivatetoprotected, enablingexpose()to pick them up via reflection