Custom timings showing on pages that arent-related #500
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 some rare circumstance a custom timing may be created before the raygun4js has fully initialized.
In this case then event is queued for sending later.
In some very rare cases by the time the event is sent the page (and therefore the parent resource) has changed.
This can result in some timings being miss-attributed to the wrong page.
This pr tries to get the parent resource before the event is queued.