-
Notifications
You must be signed in to change notification settings - Fork 4
Menu options #13
Comments
Leave the wget code, remove the option. Keep the code if we later decide we need Wget for something else. |
You should add a project to the projects tab and we should fill it up with a little roadmap to some kind of final set of features. Like i mentioned before, I think a good use case for this is API testing and offering a TUI so that a user could configure a set of API tests and expectations, and that could be integrated with CI |
Lol too late.. I stripped it down. Recursive downloading is a whole thing in itself to implement, that's what I'm doing right now is getting that set up and writing tests for it. |
feel free to add to the project tab :D |
I cant it doesnt let me, you either have to give me access or create one and let me add to it. |
I can see it we good! |
I think offering HTTP requests with any of those 3 options (HTTP custom, cURL, or wget) is just pointless, as I cannot see any reason why someone would want to send a GET or POST request with wget as opposed to cURL.
I think I am going to strip all the functionality of WGET aside from recursive downloads (the only thing it can do that curl cannot.)
AND
remove the option for custom HTTP requests (using reqwest) unless someone can provide me with a good reason not to. Because i just cannot think of any. Whether you use libcurl or some custom client.. it's all the same. and curl allows you to save the command and share it to run on servers or anything else you might want to do with it.
The text was updated successfully, but these errors were encountered: