-
Notifications
You must be signed in to change notification settings - Fork 106
:encoder_opts formatter option
#130
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
Conversation
|
Nice, looks like a pretty sane approach to me (but I'm not @AndrewDryga). For testing, I think you have two options:
Maybe both is better for completeness: the integration test for testing that specifying the encoder_opts actually makes a difference in log output, the unit test to ensure that all encoder_opts are being passed through. |
|
@bvobart thanks for reviewing and providing your thoughts! Since I'm not the maintainer of this library I'd prefer not to introduce something like mocking. Also, since the integration with Jason is minimal for this feature I think the current approach should be fine for now from a maintainability perspective. Which is my main concern. I'll keep moving forward with my current approach. Thanks again for the review! ❤️ |
|
@AndrewDryga this pull request is ready for review. closes #130 |
AndrewDryga
left a comment
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.
Great work, thank you!
|
@AndrewDryga thank you for the review! I updated this pull request with your suggestions. |
|
Thank you! |
|
No, thank you! 😄 |
Wanted to get a sanity check before moving forward with other formatters to make sure I'm on the right track.
I'm not 100% sure what to do for testing. I basically need to test the behavior of Jason when passing an encoder option which seems clunky and brittle no matter how it gets implemented. At the moment I'm doing a partial regex match on a pretty printed string. Open to other ideas!