mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 16:55:59 +03:00
[GH-ISSUE #62] Fast URL entry #26
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#26
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @NBTX on GitHub (Aug 25, 2019).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/62
Originally assigned to: @terranblake, @NBTX on GitHub.
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 commented on GitHub (Aug 25, 2019):
I'm happy to implement this myself, but I wanted to open a discussion on the matter.
@liyasthomas commented on GitHub (Aug 25, 2019):
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 commented on GitHub (Aug 25, 2019):
@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 commented on GitHub (Aug 25, 2019):
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 commented on GitHub (Sep 6, 2019):
#93 needs similar kinda approach
@terranblake commented on GitHub (Sep 28, 2019):
@liyasthomas and @NBTX i'd like to take this one for hacktoberfest 😄
@liyasthomas commented on GitHub (Sep 28, 2019):
@terranblake you are free to contribute to this 🔥👌 assigning to you.
@terranblake commented on GitHub (Sep 28, 2019):
@liyasthomas for this feature to be implemented, i do have a couple questions about a proposed design.
pathfield be removed as a part of the solution?permalinkandshow codebuttons below theurlfield on the same plane asimport cURL?@liyasthomas commented on GitHub (Sep 28, 2019):
@terranblake yes you can.
permalink&show codecan be moved to bottom of the section.currently
pathis appended to request, you must resolve that while making changes.there are bindings for
pathin various methods, you must resolve that too.@NBTX commented on GitHub (Sep 28, 2019):
@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,
pathis 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
pathinput 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 commented on GitHub (Oct 8, 2019):
Hopping on this one tonight. Will keep this issue updated.
@terranblake commented on GitHub (Oct 8, 2019):
@liyasthomas commented on GitHub (Oct 8, 2019):
@terranblake you tested? Any bugs?
@terranblake commented on GitHub (Oct 8, 2019):
Query params are imported directly into the parameters section. I am having an issue with the
Refererfield of the request getting blown up...@liyasthomas commented on GitHub (Oct 8, 2019):
Lemme take a look at it and possibly help you 🙂
@terranblake commented on GitHub (Oct 8, 2019):
Alrighty. I'll fork. One sec
@terranblake commented on GitHub (Oct 8, 2019):
Should be available on this branch
@dihmeetree commented on GitHub (Feb 24, 2020):
This seems to have been implemented. Can this be /closed? Or this still open for discussion? :) @NBTX @liyasthomas
@liyasthomas commented on GitHub (Feb 24, 2020):
I afraid this feature was incomplete and branch went stale. Lemme run some tests.
@JacobAnavisca commented on GitHub (Feb 25, 2020):
Heyo! Just made a PR for this https://github.com/liyasthomas/postwoman/pull/603
used a regex and I did some testing but might be good for others to try it out as well