fix(experiments): update breakdown_value type. #41867
Merged
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
The
BreakdownKeyTypeis not great.Ideally, you want your types to be extended via unions or derived via utility types. In the case of
BreakdownKeyType, you would like to treat it as a primitive and either allow it to be used as an array or make it nullable in the final type or variable.Changes
We were inadvertently deriving
BreakdownKeyTypeas an array when it already includes the array form as a union. That was causing some problems with type inference, which we fixed by adding a type assertion.This change acknowledges the weirdness of
BreakdownKeyTypeand documents why we are using primitives instead when definingbreakdown_values.How did you test this code?
👉 Stay up-to-date with PostHog coding conventions for a smoother review.
Changelog: (features only) Is this feature complete?