Allow none filter in chargefilterusage (default case)#353
Merged
vincent-pochet merged 2 commits intogetlago:mainfrom Jan 8, 2026
Merged
Allow none filter in chargefilterusage (default case)#353vincent-pochet merged 2 commits intogetlago:mainfrom
vincent-pochet merged 2 commits intogetlago:mainfrom
Conversation
vincent-pochet
approved these changes
Jan 8, 2026
Contributor
|
Thank you @harshitgupta412 for this pull request. |
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
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.
when getting current usage, the current api returns None in value for Default case. ChargeFilterUsage BaseModel does not allow this and so the function
client.customers().current_usageerrors out with