Closed sharifhsn closed 1 year ago
Let me know if there are any bikeshed quibbles with the naming of methods and I'll be happy to change them!
Awesome, thank you very much!
Could you please add an entry to the "unreleased" section in CHANGELOG.md
to briefly describe the breaking change? That would help me with creating the next release.
One last thing: do you feel it's necessary to add documentation to the new PrinterBuilder
struct? I feel like the builder functions are self-documenting, but perhaps the new
function and build
function should have examples for those unfamiliar with the builder pattern.
One last thing: do you feel it's necessary to add documentation to the new PrinterBuilder struct? I feel like the builder functions are self-documenting, but perhaps the new function and build function should have examples for those unfamiliar with the builder pattern.
Thank you for your concern. Adding documentation is always great, but I wouldn't see this as a requirement for this PR. This changeset already improves hexyl as a library significantly.
There was no documentation before because - to be honest - I only support hexyl-the-public-library in a "best effort" manner.
So I suggest we merge this as is, but new PRs are always welcome of course!
That should be everything!
As discussed in my previous pull request, this pull request deprecates using the new method directly on the
Printer
struct, preferring thePrinterBuilder
struct for the builder pattern. This is a breaking change forhexyl
as a library.