-
Notifications
You must be signed in to change notification settings - Fork 925
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
fix!(state): use node blob type instead of app type to fix inconsistent unmarshalling #2338
Conversation
Going to rework this PR after a good suggestion from @vgonkivs to just have blob service take an interface for submitting data instead of moving blob/service to nodebuilder |
It will help to break dependency blob -> state |
a382624
to
bc97346
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One small comment. Other than that LGTM. Thank you.
Codecov Report
@@ Coverage Diff @@
## main #2338 +/- ##
==========================================
- Coverage 50.89% 50.86% -0.04%
==========================================
Files 154 154
Lines 9746 9742 -4
==========================================
- Hits 4960 4955 -5
+ Misses 4352 4350 -2
- Partials 434 437 +3
|
1e4f76d
to
e7be89e
Compare
75bae3f
to
2a3a8d9
Compare
Breaks API to v0.2.0
Because state.SubmitPayForBlob was using apptypes.Blob, which cannot be unmarshalled from a node blob.Blob JSON object, it was requiring two separate types downstream. Now both blob Service and state Service use blob.Blob type.
The caveat here is that I had to move the blob service implementation inside nodebuilder, as we do for header service as well - due to import cycles. This is not a long term solution, as eventually we will share the blob type with appThis means introducing an interface in blob.Service called blob.Submitter to avoid that state module import.