This PR solves the above issue by selecting extended types before nodes get removed/cleaned during content selection.
Before:
Adding extended types via the command line was functional, but adding via the API with addExtractor was producing null extended values when custom extractors lacked a content key. This is because root-extractor.js was executing selectExtendedTypes after content extraction, which involves the removal of various nodes in the DOM tree. Consequently, some extended types failed to appear.
After:
After this PR, selectExtendedTypes executes before content fetching in order to traverse the DOM before cleaning.
721
This PR solves the above issue by selecting extended types before nodes get removed/cleaned during content selection.
Before:
addExtractorwas producing null extended values when custom extractors lacked acontentkey. This is becauseroot-extractor.jswas executingselectExtendedTypesafter content extraction, which involves the removal of various nodes in the DOM tree. Consequently, some extended types failed to appear.After:
selectExtendedTypesexecutes before content fetching in order to traverse the DOM before cleaning.