-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Transact action should support common encoding formats- JSON, Transit, edn, and Form-POST #62
base: master
Are you sure you want to change the base?
Conversation
…, edn, and Form-POST
Unrelated to this PR but I noticed that the |
It does now :) -- nice catch. |
I think we'll want to add |
@ohpauleez I spent some time thinking about this PR and thought that extracting In the future this could even be made configurable so that developers could specify which content-types are supported – a consequence of this is that such information could be feed into specification generation tooling for things like Swagger. I'd be happy to adopt this PR and hash this out if you're up for it. |
Alternatively, |
Ping @ohpauleez just following up. This PR is related to issue #78 as well. |
I'd really see this PR make it in to send edn instead of json |
@ohpauleez I'm guessing this work is sitting on the back burner. Would it be ok if I pushed it forward? |
This addresses issue #45
Resolving the "payload" parameter for transact is handled by a separate function.
Currently, this function also grabs form params as a last effort (which are not nested under
payload
).