You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As I see this people work like this: a) try url in browser actually b) copy to our input c) modify PUT params and rerun. So it have to be lending input where ppl paste/drag ready made url from browser. And then we parse url to parts like
Protocol: HTTPS
Host: github.com
Path: /liyasthomas/postwoman/issues/new
Params:
assignees=${_assignees}
labels=${_labels}
template=feature_request.md
title=${_title}
It will make easy to identify and modify params/ opens door to macro and scripting (instead or with pre-scripting). And will build ground to further WDSL/Swagger/gRPS impl(s)
The text was updated successfully, but these errors were encountered:
We currently have such a similar implementation. URL is parsed and populated to diff categories including parameters, payload, headers etc.
Users can make a request and we append it's attributes to URL as parameters making it a universally sharable link. Anybody with that link can replicate the same request from the other side by just visiting it.
As I see this people work like this: a) try url in browser actually b) copy to our input c) modify PUT params and rerun. So it have to be lending input where ppl paste/drag ready made url from browser. And then we parse url to parts like
Protocol: HTTPS
Host: github.com
Path: /liyasthomas/postwoman/issues/new
Params:
assignees=${_assignees}
labels=${_labels}
template=feature_request.md
title=${_title}
It will make easy to identify and modify params/ opens door to macro and scripting (instead or with pre-scripting). And will build ground to further WDSL/Swagger/gRPS impl(s)
The text was updated successfully, but these errors were encountered: