twenty

Elgato_dark/twenty

Fork 0

mirror of https://github.com/twentyhq/twenty synced 2026-05-05 06:18:30 +00:00

Commit graph

Author	SHA1	Message	Date
martmull	da064d5e88	Support define is tool logic function (#17926 ) - supports isTool and timeout settings in defineLogicFunction in apps and in setting tabs definition - compute for all toolInputSchema for logic funciton, in settings and in code steps <img width="991" height="802" alt="image" src="https://github.com/user-attachments/assets/05dc1221-cac9-45a3-87b0-3b13161446fd" />	2026-02-16 10:43:29 +01:00
martmull	a4ed043d43	Logic function refactorization (#17861 ) As title	2026-02-12 11:40:49 +01:00
Charles Bochet	67a98f77e3	Refactor workflow-logic-function-interaction (#17699 ) # Refactor workflow–logic function interaction ## Why Workflow code steps and standalone logic functions shared the same build layer and DB layer, which blurred two use cases: code steps belong to a workflow version; standalone functions are deployable units. That made workflow code steps harder to own and evolve. ## Goal Treat code steps as workflow-owned: build and run them in workflow context, and expose workflow-scoped APIs so the editor can load, test, and save code step source without going through the generic logic-function layer.	2026-02-05 00:46:55 +00:00

Author

SHA1

Message

Date

martmull

da064d5e88

Support define is tool logic function (#17926 )

- supports isTool and timeout settings in defineLogicFunction in apps
and in setting tabs definition
- compute for all toolInputSchema for logic funciton, in settings and in
code steps

<img width="991" height="802" alt="image"
src="https://github.com/user-attachments/assets/05dc1221-cac9-45a3-87b0-3b13161446fd"
/>

2026-02-16 10:43:29 +01:00

martmull

a4ed043d43

Logic function refactorization (#17861 )

As title

2026-02-12 11:40:49 +01:00

Charles Bochet

67a98f77e3

Refactor workflow-logic-function-interaction (#17699 )

# Refactor workflow–logic function interaction

## Why

Workflow code steps and standalone logic functions shared the same build
layer and DB layer, which blurred two use cases: code steps belong to a
workflow version; standalone functions are deployable units. That made
workflow code steps harder to own and evolve.

## Goal

Treat code steps as **workflow-owned**: build and run them in workflow
context, and expose workflow-scoped APIs so the editor can load, test,
and save code step source without going through the generic
logic-function layer.

2026-02-05 00:46:55 +00:00

3 commits