Allow for objects to be passed to lazyDefine, avoiding repeat calls #321
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.
In our mob pairing session called "Making Dotcom Fast" we ran into an issue where we're calling
lazyDefine
over 200 times in quick succession. This becomes quite expensive ascancelAnimationFrame
is O(n) and we're calling it 200 times meaning we end up with thousands of iterations that ultimately do nothing.In order to prevent this cost on page load, we can overload
lazyDefine
to take an object of element->callback pairs, meaning we only callobserve()
once. This then needs a tiny refactor on the consumer side, but it turns this:into this: