Customization of HTTP/JSON output #131
Merged
Conversation
This file contains 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
added 2 commits
September 9, 2016 20:54
This allows clients to utilize the capabilities of the class while being able to add additional properties. This fixes #114
|
@whiskeysierra I will check that. But from what I just see I think it will match 100% of my use case! Thanks for hard working on it :) |
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.
Fixes #114
@kakawait
Adds public
prepareandformatmethods to theDefault- andJsonHttpLogFormatter. Prepare returns a data structure that can be modified (List<String>andMap<String, Object>respectively). The format method renders the corresponding data structure into a string.The intended use case is to write a custom formatter that has an instance of one of those two and uses it to generate and customize the output.