Skip to content
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

[task] Avoid defining incomplete constant output schemas for actions or triggers that don't have a fixed output schema structure. #1873

Open
ivicac opened this issue Dec 20, 2024 · 0 comments
Assignees
Labels
backend Concerning any and all backend issues task Task to do

Comments

@ivicac
Copy link
Contributor

ivicac commented Dec 20, 2024

  • It brings more confusion in the Data Pill panel as not all expected data pills are shown
  • Instead, define OutputFunction to evaluate expected schema dynamically
  • as a last resort, define a fully dynamic output schema by setting .output() to allow calling the perform method through the "Test Component" button/menu item
  • As a rule of thumb:
    • the OutputFunction should be defined when an action/trigger has dynamic output but does not connect to any external service(Var, ObjectHelper components, for example)
    • the fully dynamic output schema by setting .output() should be defined when an action/trigger has dynamic output and consumes external services(HttpClient component, for example)
@ivicac ivicac converted this from a draft issue Dec 20, 2024
@ivicac ivicac added task Task to do backend Concerning any and all backend issues labels Dec 20, 2024
@ivicac ivicac changed the title [task] Avoid define constant output schema for action/triggers if it is not possible define the whole expected structure [task] Avoid defining constant output schema for action/triggers that can't define constant output schema structure Dec 20, 2024
@ivicac ivicac changed the title [task] Avoid defining constant output schema for action/triggers that can't define constant output schema structure [task] Avoid defining half-defined constant output schema for action/triggers that can't define constant output schema structure Dec 20, 2024
@ivicac ivicac changed the title [task] Avoid defining half-defined constant output schema for action/triggers that can't define constant output schema structure [task] Avoid defining incomplete constant output schemas for actions or triggers that don't have a fixed output schema structure. Dec 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Concerning any and all backend issues task Task to do
Projects
Status: V 0.1
Development

No branches or pull requests

2 participants