Lookup source string as key to cache #42
Merged
Conversation
This file contains 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
Uses the source string as the key for cache lookup when rendering a localized translation. As a fallback, if the entry is not found, the logic also uses the hash of that source string as a key for cache lookup.
* Bumps `TXNative.version` to 1.0.1 * Updates CHANGELOG with the changes implemented for v1.0.1
n1k0sv
approved these changes
Sep 23, 2021
Merged
Closed
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.
Uses the source string as the key for cache lookup when rendering a
localized translation.
As a fallback, if the entry is not found, the logic also uses the hash
of that source string as a key for cache lookup.