-
Notifications
You must be signed in to change notification settings - Fork 295
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
feat: request observers to intercept requests and responses #365
Conversation
Unit Test Results 🚀649 tests ±0 648 ✅ - 1 2m 37s ⏱️ -22s For more details on these failures, see this check. Results for commit b1e41ff. ± Comparison against base commit 9669272. ♻️ This comment has been updated with latest results. |
@@ -494,6 +502,10 @@ public void run() { | |||
L.v("[ConnectionProcessor] Response was a unknown, will retry"); | |||
rRes = RequestResult.RETRY; | |||
} else { | |||
// notify observers for the response |
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.
add tests for this
also fix codacy |
le conflic |
we might omit this PR for now, this was needed for content update from RQ but we are not doing that anymore |
This is needed for module content's fetching mechanism