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
Maybe this is an optimization problem, or maybe it's a bad idea to read several dozen mb of binary files as a base64 encoded json property in order to upload it to blob storage.
We should consider adding a way to declare the body of an api as coming from a file instead of being declared as a binary json property. Something like a top level property like bodyFile or input.
Should also add a command-line switch named -i|--input in order to provide multiple base paths. Reading files which are not part of the template folder would be relative to one of those paths. It should also be impossible for a workflow to read any file that isn't a sub-path of an --input directory.
The text was updated successfully, but these errors were encountered:
Maybe this is an optimization problem, or maybe it's a bad idea to read several dozen mb of binary files as a base64 encoded json property in order to upload it to blob storage.
We should consider adding a way to declare the body of an api as coming from a file instead of being declared as a binary json property. Something like a top level property like
bodyFile
orinput
.Should also add a command-line switch named
-i|--input
in order to provide multiple base paths. Reading files which are not part of the template folder would be relative to one of those paths. It should also be impossible for a workflow to read any file that isn't a sub-path of an --input directory.The text was updated successfully, but these errors were encountered: