Vinícius Vaz
Vinícius Vaz
The UI for the workflows editor is not so user-friendly. There are two points we can start improving: 1. Pieces repositories sidebar (image 2): The sidebar is too compressed, affecting...
We should think the best way for editing workflows. At the first moment I see 2 options: ### 1. Recreating the workflow (like a PUT operation) **Pros:** - It is...
Allow conditional forms in frontend from pydantic models Ref: https://docs.pydantic.dev/latest/concepts/unions/#discriminated-unions
Create a workflow gallery in domino-docs repository. This gallery can use as source of data files from the same repository as pieces gallery. Our goal here is to provide the...
We don't have workflow description, would be good to have it. To do that we need: - Update `workflows` db table adding description as string field - Update rest api...
Currently all data types in `display_results` are being converted to base64 string when serializing to xcom, but some of the accepted formats are already serializable, such as json and plain...
We aim to restrict the size of data stored in the BasePiece.display_result property, as these values are transmitted to the frontend for UI rendering. Allowing excessively large data might lead...
Currently we accept workflow manual trigger or scheduled triggers. Would be great to have workflows that are triggered from a webhook. In order to do that we might have to...
When running pytest in GitHub Actions, the `piece_dry_run` is executed in an external Docker environment that has no direct relation to the pytest code. While this approach offers the advantage...
In pydantic we can define range of values for numeric fields. You can define this either using custom types like [PositiveInteger](https://docs.pydantic.dev/2.3/usage/types/number_types/) or using `Field` api. Both approaches generate json schemas...