Added a solution for Dictionaries with nested objects #157
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.
A proposed solution for using dictionaries with nested objects
Corresponding issue: #151
Implemented solution
A new header type surrounded with [{}]. This will create a new object names after the cell content rather than the column title.
Usage
We can now address the issue raised in 151 with this new header
Outcome (All examples are done with only the Nested Elements options enabled):
Advantages
We can take this a step further and are able to rework the advanced country example to now include different objects as well as lists
Output
Code changes
Dict
toSubpathTypes
and changedgetSubpathTypeJson
to accomodate this new headergetKeyPath
andtrimKeySubpath
to accomodate for the 2 character identifierexportSpreadsheetJson