Feat(invoice): Add finalize zero invoice to GraphQL #2526
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
brunomiguelpinto
added
GraphQL
brunomiguelpinto
changed the title
brunomiguelpinto
changed the title
annvelents
approved these changes
Sep 3, 2024
brunomiguelpinto
force-pushed
the
feat-enable-skip-zero-invoices
branch
from
d6e4885
to
495a120
Compare
brunomiguelpinto
force-pushed
the
feat-enable-skip-zero-invoices
branch
from
20970a0
to
3820a61
Compare
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.
Context
This PR introduces a new field, finalize_zero_amount_invoice, to the Customer-related GraphQL types and input objects, as well as to the organization settings. This field is an enum type that provides options for handling invoices with a zero total amount. The enhancement allows users to specify how zero-amount invoices should be managed at both the organization and customer levels
its to enable what we did on this pr but on the frontend #2462