fix: strip non-nullable optional params in Dart/Flutter SDKs #1252
+8
−6
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.
Summary
This PR updates the Dart and Flutter SDK templates to conditionally include non-nullable optional parameters in the request params map only when they are not null, matching the behavior of the Python SDK.
Changes
templates/dart/base/utils.twigmap_parameter macrotemplates/flutter/base/utils.twigmap_parameter macroImplementation Details
Previously, all parameters were always included in the params map, which could lead to unnecessary null values being sent in API requests.
This implementation matches the Python SDK behavior (
templates/python/base/params.twig:15-17and26-28) where optional non-nullable parameters are checked withif not Nonebefore being added toapi_params.Generated Code Example
Before:
After:
Technical Details
!) for enum values when inside null checknot parameter.nullable)not parameter.required)Test Plan
Summary by CodeRabbit