extruct

extruct copied to clipboard

At present, extruct supports a HTTP API for "testing", but that carries a maintenance burden, and it invites feature-requests that may nudge it more and more into becoming a monolithic proxy service. That's not really where we want Extruct to be, I think.

Similarly with the HTTP-Client mode and the CLI tool that offers it - it's a mode of operation which probably shouldn't be our priority with extruct. I feel that if we provide a CLI client for extruct, it should probably just accept HTML through a Unix pipe or from a file, and operate on that. That way, people can use curl or wget or whatever else they like, and they won't worry about extruct's support for various HTTP client features.

Thoughts? :)

@cathalgarvey I'm probably too biased to provide valuable feedback on this, as I've implemented the CLI in the past, but I think that it is an useful feature (at least I find myself using it frequently 😄).

But I totally agree with you on that extruct should just read stuff from a file/pipe, as it makes it easier to customize the requests as much as we need using a proper tool such as curl/wget.

IMHO, we should keep the CLI, but maybe change it so that extruct doesn't make the HTTP requests.