-
Notifications
You must be signed in to change notification settings - Fork 44
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
refactor: Remove redundant txn param from fetcher start #1635
refactor: Remove redundant txn param from fetcher start #1635
Conversation
Codecov ReportPatch coverage:
@@ Coverage Diff @@
## develop #1635 +/- ##
===========================================
+ Coverage 75.54% 75.62% +0.09%
===========================================
Files 200 200
Lines 20808 20807 -1
===========================================
+ Hits 15718 15735 +17
+ Misses 4006 3994 -12
+ Partials 1084 1078 -6
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 5 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
4a74db7
to
cae673b
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.
LGTM.
It seems that a more appropriate name for the PR would be Move txn from fetcher start to init
don't you think?
I disagree with you on that :) Your suggestion suggests it doesnt already exist on init |
Is always the same value as fetcher.Init
cae673b
to
d5e0642
Compare
That's my point. It didn't. |
I mean that it was part of the Init param but nothing was done with it. |
I think you are mistaken. It was added to Init in an earlier Lens PR. |
…k#1635) ## Relevant issue(s) Resolves sourcenetwork#1623 ## Description Removes the redundant txn param from fetcher start as it is always the same value as fetcher.Init
Relevant issue(s)
Resolves #1623
Description
Removes the redundant txn param from fetcher start as it is always the same value as fetcher.Init