Cater for shapes where keys are not all strings in AddPrefixToKeys interface definition #6371
+3
−3
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
Fixes #6105
The issue comes from
AddPrefixToKeys
interface, shown below, in use cases where nested interfaces are defined asRecord<string, Model>
or{[key: string]: Model}
- it looks like Typescript has a challenge inferring such shape as it considersK
to be of typestring|number|symbol
.To solve this, we have to tell Typescript to infer the type or use a conditional statement to determine the type as shown below. Now, typescript can infer K and know its shape n-levels deep.
This Typescript playground shows what's happening - all interface definitions come from the current version of firebase-js-sdk (firebase v9.7.0). I've commented the current logic for the fix. Switch between the 2 to see how the fix solves the issue
cc @ehsannas