Skip to content

Instantly share code, notes, and snippets.

@ashwanth1109
Last active April 13, 2021 09:22
Show Gist options
  • Save ashwanth1109/bcf1baf1a1b37a9261368647389d56b4 to your computer and use it in GitHub Desktop.
Save ashwanth1109/bcf1baf1a1b37a9261368647389d56b4 to your computer and use it in GitHub Desktop.
Summary from hackathon feedback

Feedback notes

Note: Number at the end indicates the number of people raising the same issue
  • Need SAVE, VALIDATE and PUBLISH
  • Validate the iterator
  • Parameters in TEST are not persisted across flows * 2
  • Execution Traces was failing to open 50% of the time (so was only able to debug using kibana logs)
  • Node name too long failing with no indication of why it was failing * 3
  • Save JSON to s3 action required base64 encoding (in transformer expression) rather than passing a simple JSON object (transformer expression is not validated and error prone)
  • Could not understand how to provide parameters to DynamoDB action (no examples or default value provided as part of the action, and it was not clear from description) - blocked from being able to use
  • Unable to see lambda logs * 5
  • Allow to have actions with empty input or output schema * 2
  • Unable to have a no-node flow while editing
  • Hard to find button for execution traces
  • Link to source repo and action page from the flow UI
  • Preview and Test tab can be coupled together as one tab
  • Deploy time too long for quick iterative testing (i.e. deploy each change to test is not feasible) * 4
  • Execution takes too long or is stuck * 3
  • Bugs in standard actions * 2
  • Insufficient documentation
  • Worked on Devspace but fails on Devflow (Runtime error)
  • Output/input text is truncated to 2000 characters
  • Rather than invoking the whole or creating a new flow to test single node (in between the flow), would like to provide input and quickly check output for just one node while in same flow
  • Changing the function name after creation is not working well
  • Do not run Github action (in source repo) if no code-related changes have occured.
  • Info button on each action to show what data it has outputted. If too much to show that data in a popup, Use a new file which has the entire json.
  • In case of errors on action, action should show error icon and logs should be available on that action node itself (logs of only for that action that is)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment