Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ad data on resolving events #420

Merged
merged 4 commits into from Feb 15, 2022
Merged

Ad data on resolving events #420

merged 4 commits into from Feb 15, 2022

Conversation

clementFrancon
Copy link
Contributor

Description

In order to troubleshoot ad performances, we need to have some information on the current ad node being resolved

Type

  • Breaking change
  • Enhancement
  • Fix
  • Documentation
  • Tooling

* @emits VASTParser#VAST-resolving
* @emits VASTParser#VAST-resolved
* @return {Promise}
*/
fetchVAST(url, wrapperDepth = 0, previousUrl = null) {
fetchVAST(url, wrapperDepth = 0, previousUrl = null, ad = null) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do you think about renaming ad to wrapperAd to make it more explicit (especially on the markdown documentation)

Suggested change
fetchVAST(url, wrapperDepth = 0, previousUrl = null, ad = null) {
fetchVAST(url, wrapperDepth = 0, previousUrl = null, wrapperAd = null) {

@@ -129,6 +130,7 @@ export class VASTParser extends EventEmitter {
wrapperDepth,
maxWrapperDepth: this.maxWrapperDepth,
timeout: this.fetchingOptions.timeout,
ad,
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not sure if we should call it ad or parentAd or something WDYT?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wow 1 sec between our comments, ok I'll change it

Copy link
Contributor

@ZacharieTFR ZacharieTFR left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM ! 🚀

@ZacharieTFR ZacharieTFR merged commit b523550 into 4.X Feb 15, 2022
@ZacharieTFR ZacharieTFR deleted the ad-data-on-resolving-events branch February 15, 2022 09:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

None yet

2 participants