Fixes a bug that prevented using complex dictionaries within compositions #965
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.
Fixes #964.
In case of "simple" dictionary (
Record<string, number>
orRecord<string,array<number>>
, model.type was set tonumber
inparser/getModel.ts
function. But in case of composite,type
was not explicitly set and defaulted toany
.I didn't want to change this type in the
getModel
function, as it might have some other implications, so I just added another check in when to ignore a model within composition.Added 3 more test objects to the suite, so it covers all three cases.