#42 - add createInvoiceFormatter() with TenantContext parameter - #43
Merged
Conversation
xsalefter
changed the title
sbrossie
approved these changes
Aug 3, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Original ticket #42 . Decided to use overload + default method instead of just adding another
TenantContextin current method for following reason:Overload + default method : It is true that 3rd party user forced to re-implements, but current code that call this method without
TenantContextwill keep working and not breaking.Change method signature only : 3rd party need to re-implements and changes any code to pass
TenantContext, even if it is not needed (and they could just need to passnullanyway).However, I'm OK if implementation need to do the opposite. I just think this approach could support little bit better for backward compatibility.