Update t-function to support nested keys. Previous code does not handle nested key access properly #17
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
app_scaffolds/packages/react/src/lib/i18n.js
Line 39 in 455bf6e
What happened in my case is that my application does not render the initial configurations since the line above only support single-access key in JSON. The line that caused this to malfunction are the ones below:
app_scaffolds/packages/react/src/app/locations/TicketSideBar.jsx
Line 31 in 455bf6e
app_scaffolds/packages/react/src/app/locations/Modal.jsx
Line 6 in 455bf6e
With this issue, I made it so that the function will accept nested key access.