Comments (8)
wdyt, @sstrigler @isakb ?
from katt.
Feels weird. Setting content-type to 'application/x-www-form-urlencoded' and then sending sth different...
On 21 juni 2016, at 17:09, Andrei Neculau [email protected] wrote:
wdyt, @sstrigler https://github.com/sstrigler @isakb https://github.com/isakb ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub #49 (comment), or mute the thread https://github.com/notifications/unsubscribe/AABc6s6jwvEvDxhZAgv3xYDx_9GfDHK6ks5qN_6qgaJpZM4I62A2.
from katt.
you still send application/x-www-form-urlencoded, but with a JSON DSL. We already have that today
POST /foo
some{{<bar}}
is not that different, right? You do send "somequx" if bar = qux.
from katt.
Yeah, you're right. Mind boggling! B)
What if...
POST /foo
Content-Type: application/x-www-form-urlencoded
{{<payload}}
And then what if 'payload' is
{
"key1": "http://example.com http://example.com/",
"key2": "a=b"
}
On 21 juni 2016, at 17:32, Andrei Neculau [email protected] wrote:
you still send application/x-www-form-urlencoded, but with a JSON DSL. We already have that today
POST /foo
some{{<bar}}
is not that different, right? You do send "somequx" if bar = qux.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub #49 (comment), or mute the thread https://github.com/notifications/unsubscribe/AABc6ukHyE3aoB6f_hpqfJSWJqY7hH38ks5qOAQSgaJpZM4I62A2.
from katt.
I don't see how that plays into this. We only parse the DSL once, not twice, not until it stabilizes. If payload was "{{<payload2}}", regardless of the content-type, it's not like we would expand payload2.
from katt.
Ok ok, but know you've read my comment as just one remark. At least I think so.
My first concern is that when you have old style blueprints that start with a {{<param}} with the new DSL you'd think that's a JSON that follows. So you probably have to make sure there is no second { before interpreting as the new DSL.
No?
On 21 juni 2016, at 17:47, Andrei Neculau [email protected] wrote:
I don't see how that plays into this. We only parse the DSL once, not twice, not until it stabilizes. If payload was "{{<payload2}}", regardless of the content-type, it's not like we would expand payload2.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub #49 (comment), or mute the thread https://github.com/notifications/unsubscribe/AABc6q3O9PSAENnK9n45BwMfCQBTx4ZQks5qOAd-gaJpZM4I62A2.
from katt.
Aha, I see. That is a valid concern but I guess i should clarify the detection rule (i.e. "{[^{]" since that's not valid JSON), thus make it more specific, or say that we now try parsing as JSON and use the DSL, and on failure we default to simple text, like before.
Worth thinking about.
21 juni 2016 kl. 18:07 skrev Stefan Strigler [email protected]:
Ok ok, but know you've read my comment as just one remark. At least I think so.
My first concern is that when you have old style blueprints that start with a {{<param}} with the new DSL you'd think that's a JSON that follows. So you probably have to make sure there is no second { before interpreting as the new DSL.
No?
On 21 juni 2016, at 17:47, Andrei Neculau [email protected] wrote:
I don't see how that plays into this. We only parse the DSL once, not twice, not until it stabilizes. If payload was "{{<payload2}}", regardless of the content-type, it's not like we would expand payload2.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub #49 (comment), or mute the thread https://github.com/notifications/unsubscribe/AABc6q3O9PSAENnK9n45BwMfCQBTx4ZQks5qOAd-gaJpZM4I62A2.—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
from katt.
I am a bit skeptical, but can see the pain of having to application/x-www-form-urlencoded payloads.
+/- 0
🎱
from katt.
Related Issues (20)
- Erlang code as a step HOT 2
- matching fails
- Errors should not be printed to stdout
- Confusing error message when katt script file does not exist
- float Params get multiplied by factor 10 HOT 1
- Cannot store response Integers in Param HOT 2
- `Actual` is unbound/undefined in `runtime_validation` type. HOT 1
- Not possible to validate response as json if no content-type in response header
- Not possible to specify multiple http response codes
- Katt compile error due to get_stacktrace error in meck HOT 3
- Storing key value will always succeed even if key does not exists. HOT 2
- Allow secret params that are not logged HOT 1
- Update katt to avoid deprecated function call, in preparation for OTP25. HOT 1
- Prepare katt for jsx 3.0 HOT 1
- travis to github actions HOT 1
- broken with rebar 3.14 HOT 1
- Possibility to give hackney options
- support for recent rebar3 version HOT 5
- CLI tool as docker image
- handle request errors
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from katt.