-
Notifications
You must be signed in to change notification settings - Fork 113
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
Deprecate Server and HTTP Client mode? #63
Comments
@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 IMHO, we should keep the CLI, but maybe change it so that |
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 forextruct
, it should probably just accept HTML through a Unix pipe or from a file, and operate on that. That way, people can usecurl
orwget
or whatever else they like, and they won't worry aboutextruct
's support for various HTTP client features.Thoughts? :)
The text was updated successfully, but these errors were encountered: