Resources. Don't return a cached value when pass new args #4333
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
The issue was because we cache the value in the current composition, and the next composition returns the cached value. There weren't an issue if we just call one `stringResource` after another because those are different compositions. Fixes #4325
igordmn
changed the title
pjBooms
approved these changes
Feb 20, 2024
igordmn
added
changelog: prerelease fix
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.
The issue was because we cache the value in the current composition, and the next composition returns the cached value.
There weren't an issue if we just call one
stringResourceafter another because those are different compositions.Fixes #4325