Skip to content
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

fix: invoices query payment_dispute_lost filter #2339

Merged
merged 1 commit into from
Jul 26, 2024

Conversation

ancorcruz
Copy link
Contributor

Context

Whenever payment_dispute_lost filter had a value other than nil it was returing only inovoices with payment_dispute_lost,

hence, when the filter had a false value, it still returns only invoices with a payment dispute lost.

Description

This change fixes the filter by providing the proper scoping base on the value of the filter.

@ancorcruz ancorcruz self-assigned this Jul 26, 2024
Whenever `payment_dispute_lost` filter had a value other than `nil` it
was returing only inovoices with `payment_dispute_lost`,

hence, when the filter had a `false` value, it still returns only
invoices with a payment dispute lost.

This change fixes the filter by providing the proper scoping base on the
value of the filter.
@ancorcruz ancorcruz force-pushed the fix-invoices-query-payment-dispute-lost-filter branch from a3c0c72 to dcb1096 Compare July 26, 2024 11:41
@ancorcruz ancorcruz merged commit d19994b into main Jul 26, 2024
6 checks passed
@ancorcruz ancorcruz deleted the fix-invoices-query-payment-dispute-lost-filter branch July 26, 2024 11:53
abdussamadbello pushed a commit to abdussamadbello/lago-api that referenced this pull request Aug 8, 2024
## Context

Whenever `payment_dispute_lost` filter had a value other than `nil` it
was returing only inovoices with `payment_dispute_lost`,

hence, when the filter had a `false` value, it still returns only
invoices with a payment dispute lost.

## Description

This change fixes the filter by providing the proper scoping base on the
value of the filter.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants