Fast URL entry

[NBTX]

Is your feature request related to a problem? Please describe.
No.

Describe the solution you'd like
Similar to Postman's interface, I think we should make the URL entry a single bar at the top, with the method on the left. Then we should just parse the URL and fill in the relevant information.

We could keep the extra sections but this would make Postwoman a lot more intuitive and faster to use.

Describe alternatives you've considered
n/a

Additional context

As shown, Postman parses the URL as it is entered and automatically fills in the relevant sections.

[NBTX]

I'm happy to implement this myself, but I wanted to open a discussion on the matter.

[liyasthomas]

This fact might surprise you: other than seeing some screenshots on internet, I haven't used Postman or seen its UI (this is just because, my 7 year old pc can't afford to run another Electron app). Afterall, I didn't intend to create an alternative to Postman, in my opinion this project should outperform any other such tools, since its lightweight, faster & opensource.

If there's any feature we'd like to add, all are free to discuss here. Everything is better when there's freedom and customisation in it.

[liyasthomas]

@NBTX see #63 and share your thoughts. Me too think this is an essential feature somehow I forgot at the first place. My bad. Anyway thanks for pulling it up.

[NBTX]

I'm actually only drawing the parallel to Postman's interface from experience, rather than because the names are similar, and this is the UI I'm used to - but this, as I said is something I would find useful.

I already very much prefer Postwoman because it's so much lighter. Even on my pretty decent systems Postman takes upwards of 7 seconds to start up, and then usually has several annoying pop ups to deal with.

[liyasthomas]

#93 needs similar kinda approach

[terranblake]

@liyasthomas and @NBTX i'd like to take this one for hacktoberfest 😄

[liyasthomas]

@terranblake you are free to contribute to this 🔥👌 assigning to you.

[terranblake]

@liyasthomas for this feature to be implemented, i do have a couple questions about a proposed design.

1. can the path field be removed as a part of the solution?
2. can i move the permalink and show code buttons below the url field on the same plane as import cURL?

[liyasthomas]

@terranblake yes you can. permalink & show code can be moved to bottom of the section.

currently path is appended to request, you must resolve that while making changes.

there are bindings for path in various methods, you must resolve that too.

[NBTX]

@terranblake I imagine you would just use the JavaScript URL object:
const target = new URL("https://example.com/test");

In which case you can just get .path, .host/.hostname, etc.
As @liyasthomas mentioned, path is in a separate variable so you will need to split the URL and handle them separately but part of the goal of this ticket is to have the entire URL (querystring and all) handled in a single input box as it is with postman.

So to answer your question, you can remove the path input box and have a single input box for the full URL but obviously we still need the path to be handled as a separate variable.

[terranblake]

Hopping on this one tonight. Will keep this issue updated.

[terranblake]

This is what I have so far. Nothing too crazy.

[liyasthomas]

@terranblake you tested? Any bugs?

[terranblake]

Query params are imported directly into the parameters section. I am having an issue with the Referer field of the request getting blown up...

[liyasthomas]

Lemme take a look at it and possibly help you 🙂

[terranblake]

Alrighty. I'll fork. One sec

[terranblake]

Should be available on this branch

[dihmeetree]

This seems to have been implemented. Can this be /closed? Or this still open for discussion? :) @NBTX @liyasthomas

[liyasthomas]

I afraid this feature was incomplete and branch went stale. Lemme run some tests.

[JacobAnavisca]

Heyo! Just made a PR for this #603
used a regex and I did some testing but might be good for others to try it out as well