chore: cache flags, distinct id and anon id in memory to avoid file IO every time #177
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.
💡 Motivation and Context
Closes #176
Only read the value from the storage if it's not in memory yet.
Setters always overwrite the value in the storage and memory.
Storage only will be accessed the very first time unless the value changes async (eg flags), then the memory value is also updated.
This should reduce the main thread warnings.
All values are read and updated using lockers already.
💚 How did you test it?
unit tests already exist and they are all green
📝 Checklist