fix: fixes buffering for legacy destinations #1067
Merged
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.
Fixes the Classic Destinations buffering to properly buffer events while not loaded
Fixed
shouldBuffer
check as the starting state changed fromfalse
toundefined
for ready/initialized. Hence events were bypassing buffer all the time.Changed the behaviour of
scheduleFlush
as previously it was being called after the timeout and ignoring if the plugin had finished initializing. The retry would work properly if the plugin throws an error but Bing/FB don't hence it was marking those events as sent.onReady
andonInitialized
instead of retrying at intervals.I've included a changeset (psst. run
yarn changeset
. Read about changesets here).