Repository navigation
fix: allow omitted query parameters in API client requests - #224
Draft
Kayvan-Zahiri wants to merge 1 commit into
Draft
Kayvan-Zahiri wants to merge 1 commit into
Kayvan-Zahiri wants to merge 1 commit into
Conversation
Code Review by Qodo🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)
Great, no issues found!Qodo reviewed your code and found no material issues that require reviewTip of the day💡 Did you know, you can open the rule or relationship behind a finding in one click |
PR Summary by QodoAllow omitted query parameters in API client requests
AI Description
Diagram
High-Level Assessment
Files changed (2)
|
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.
Problem
Calling the public
ApiClient.call_api('/addresses', 'GET')without query parameters raisesTypeError: 'NoneType' object is not iterablebefore reaching the transport. The same occurs for all seven supported HTTP methods, despitequery_params=Nonebeing the documented default. Generated resource methods that already supply an empty list are unaffected.Change
Normalize absent query parameters to an empty list before applying the existing query serialization helper. Populated parameters continue through the same helper.
Add a public API-client regression with 28 subcases across all seven HTTP methods: omitted parameters, explicit None, empty lists, and populated lists. The transport is mocked; no account credentials or live API calls are needed. Before the fix, the 14 omitted/None cases error. Afterward all 28 pass and the expected outgoing URL or query fields are checked.
Validation
git diff --checkpasses.This file is generated, so maintainers may also wish to carry the normalization into the generation workflow.