feat(types): enhance TypedReturn to support primitive arrays #25
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
When using
get
on a dynamic config with a fallback value, TypeScript returningArray<unknown>
for all fallbacks of type array. This forced the use of type assertions (as
) to get the correct typing, which isn't ideal for type safety.Solution
Enhanced the
TypedReturn
type to properly handle arrays of primitive types (string, number, boolean) by recursively processing array element types. This maintains type safety while supporting the full range of JSON-compatible types, including nested arrays of primitives.Testing