[IAppConfig] returns non lazy value while searching for lazy one #43247
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.
There is this possible situation where your part of code is using already existing config value. This config value needs to be switched to lazy to improve performance, but the only way to store a value as
lazy
is:setValueString()
with the argumentlazy: true
and the config value itself.updateLazy()
on the app/key pair without the need of the content of the config value.the
updateLazy()
could be run at one point of the migration, or later on, but there is room for a use case where an app is requesting a lazy config value still stored as non lazy in the database