-
Notifications
You must be signed in to change notification settings - Fork 9
process POST request body and pass it to the action #179
Comments
Can you elaborate an example of what is missing? Do you want to handle POST requests? |
Btw: do you mean |
Yes, I'd like to be able to POST data to a local dev server and make use of the fact that the pipeline only fetches markdown if there isn't already a |
I don't think we should mix things here. Everything coming from the request should be in |
I can see your concerns. On the other hand, this is how skipping the fetch step in the pipeline was designed by @trieloff (and used in the authoring POC from the Berkeley hackathon), and this change here would allow developers/content authors to make use also in local development. It could come in handy for "as you type" markdown previewing at some point... I'm open to refactoring all of it and propose to discuss the implementation details in #180 and adobe/helix-pipeline#236 respectively. |
ok, I was confused. yes, it should populate all action params, like openwhisk does:
|
🎉 This issue has been resolved in version 2.12.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Fixed in 4292fc7: top level properties in the request body will be passed as action params. |
Like openwhisk, the
helix-simulator
should process the request body and provide it to the action.The text was updated successfully, but these errors were encountered: