fix: STRF 9873 make get
etc. compatible with concat
return value
#173
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.
What? Why?
#171 inadvertently broke an edge case where the
concat
helper is used to dynamically generate property paths.With the original
get
andoption
helpers, this only worked with top-level properties (not nested properties) due to an implicittoString
conversion here. This PR modifies those helpers to accept both top-level and nested property paths generated byconcat
.Edit: During testing & review, I noticed that the old
get
helper would retrieve empty string keys (get({'': 0}, '')
would return0
) and have made changes to match that behavior.How was it tested?
Unit tests have been added to cover cases where
concat
is used to generate property paths for helpers modified in #171.cc @bigcommerce/storefront-team