You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As mentionned in #359 (comment) for a Ad Pod that have multiple Ad elements with unique sequence attributes inside a VAST but are not in ascending order the resolveAll() method will return only the first Ad element.
Meaning that resolveAll() return the first Ad element found in VAST for any VAST that contain an Ad Pod with:
sorted in descending order (e.g for Ad sequence3>Ad sequence2>Ad sequence1 it return Ad sequence3)
non sorted Ad elements (e.g for Ad sequence1>Ad sequence3>Ad sequence2 >it return Ad sequence1)
Note: When the VAST is parsed using basic methods (vastClient.get, vastParser.parseVAST, vastParser.getAndParseVAST etc..) all VAST elements are correctly parsed and returned inside a JSON object. If an Ad pod is unordered the parsing result with return parsed elements in the same order.
Please comment this issue if you have an express need for it. If so we will add the feature. In the meanwhile feel free to contribute by creating a pull request to add the support of this feature! 💪
The text was updated successfully, but these errors were encountered:
As mentionned in #359 (comment) for a Ad Pod that have multiple Ad elements with unique sequence attributes inside a VAST but are not in ascending order the resolveAll() method will return only the first Ad element.
Meaning that resolveAll() return the first Ad element found in VAST for any VAST that contain an Ad Pod with:
Note: When the VAST is parsed using basic methods (vastClient.get, vastParser.parseVAST, vastParser.getAndParseVAST etc..) all VAST elements are correctly parsed and returned inside a JSON object. If an Ad pod is unordered the parsing result with return parsed elements in the same order.
Please comment this issue if you have an express need for it. If so we will add the feature. In the meanwhile feel free to contribute by creating a pull request to add the support of this feature! 💪
The text was updated successfully, but these errors were encountered: