Thanks for the comment. That's a good point.
Initially, I was thinking of covering all initial uncovered requests.
However:
- t_should_relay_response
is quite a sensitive function for large changes.
- The patch covers a particular edge case related to a particular issue.
- Spreading the context may disrupt the clarity of the edge case and code.
Moving forward with atomic features was a better approach for me.
According to the questions, it seems the feature's purpose is much clearer now.
If no objections, then I'll cover the rest within this feature branch.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.