Create empty subscriptions cache objects directly instead of cloning #4814
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.
Create empty subscriptions cache objects directly instead of cloning
Pull Request Type
Description
As the empty subscriptions cache object is so simple, we might as well just create it directly, instead of going through
JSON.stringify
andJSON.parse
. Especially for the posts cache, the cloning made no sense, as it uses theposts
property but we were cloning an object with avideos
property, so each post cache entry contained an unusedvideos: null
property.If the cache objects get more complex in the future, we can always move the creation code into a function that returns the objects, that will still be faster than going through
JSON.stringify
andJSON.parse
, which also create temporary strings that then need to get garbage collected.Testing
Desktop