-
Notifications
You must be signed in to change notification settings - Fork 60
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
Add "readwire" interface to *some* Graphene Types. #65
base: develop
Are you sure you want to change the base?
Conversation
This is useful when you want to *read* the serialized wire protocol back into objects-in-memory. Although this is rarely used on the client side of graphene networks, at least one particular use case (BitShares blind transfers) exists. To clarify: this is __bytes__ method in reverse. The `_readwire` interface and method signature are pretty horrid, so some redesign might be required.
Codecov Report
@@ Coverage Diff @@
## develop #65 +/- ##
===========================================
- Coverage 98.69% 98.34% -0.35%
===========================================
Files 24 24
Lines 1452 1515 +63
Branches 130 135 +5
===========================================
+ Hits 1433 1490 +57
- Misses 16 19 +3
- Partials 3 6 +3
Continue to review full report at Codecov.
|
Would it be possible to add unit tests for those? |
Instead of calling those methods _rewrite, can we have them |
This is useful when you want to read the serialized wire protocol back into objects-in-memory. Although this is rarely used on the client side of graphene networks, at least one particular use case (BitShares blind transfers) exists.
To clarify: this is
__bytes__
method in reverse.The
_readwire
interface and method signature are pretty horrid, so some redesign might be required.