feat: Request classes can customize the LogFile class #16
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…her request and response headers should be logged
jwadhams
commented
Oct 30, 2024
bbene
approved these changes
Oct 30, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This feature is designed to allow a child of AbstractRequest to decide which request headers and response headers should be logged by
LogFile.The current approach (which is covered in
LogFileTest::testRequestHeadersInRequestClassandLogFileTest::testResponseHeadersInRequestClass) is that the child Request would overridegetLogFileHelperto return a new class instance. This can of course customize any part of the LogFile class, but I introduced this change so that it could overrideinterestingResponseHeadersand the newinterestingRequestHeaders