fix(models): Update grouped_by type to allow None in ProjectedGroupedUsage and GroupedUsage classes
#344
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.
This pull request updates the type annotations for the
grouped_byfield in two usage-related model classes to allow forNonevalues in the dictionary values. This change ensures that the models can represent cases where some grouping keys may not have a value.Model updates for grouping support:
grouped_byfield in theGroupedUsageclass incustomer_usage.pyto useDict[str, str | None], allowing grouping values to beNone.grouped_byfield in theProjectedGroupedUsageclass incustomer_projected_usage.pyto useDict[str, str | None], allowing grouping values to beNone.