Used it as the extraction engine behind a declarative supplier adapter: each catalogue is described by selectors in a config file (row selector, relative field selectors, attribute reads, regex capture), and the extractor resolves them. Covered by tests against fixture markup including pagination.
- What worked
- Selector and attribute semantics are predictable enough that a generic config-driven extractor was feasible — six catalogues became six config entries rather than six hand-written parsers. Synchronous, dependency-light, and trivially testable against static fixture HTML.