Fix: omit optional invoice contents from json sent to lexoffice #5
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.
It would previously for example always send an empty
paymentConditions { ... }
thingy and then lexoffice complained that thepaymentLabel
is too short.Not all of the
omitempty
fields are really optional (for examplenetAmount
orgrossAmount
must be sent, depending on taxType) - but they shouldn't be sent with null-values when they are not set.