陈杨文

> So if i understand correctly, you dont care about the flow UI part and interested in triggers. not excatly, activepieces can orchestration triggers is very lovely. > I understand...

> For example why would someone prefer activepieces slack piece more than official slack npm? e.g. I can define the template by my own, activepieces can not have all params...

Hi, maybe the time is't right, I will summary some of my thoughts here. - I want a bussiness orchestration engine - Can invoke bussiness related code easily, without expose...

> I guess we could have a flag for this, that way you could also revert it back if you want to. That will do, `setExecuteMode` or somthing ? Only...

> What if you wrapped the builder in another Promise? Alternatively, make the `read` function non-async: > > ``` > read(): Promise { > return this.em.applyFilters(this.Entity.name, {}, {}, 'read').then(result =>...

`applyFilters` is the major usecase, but I also return qb when I want to open an possible extension point like ```ts // allow child class to add static conditions protected...

> > protected async createQueryBuilder(): Promise { > > But what's the point in having that method async? What other use cases than the filters can you think of that...

Is it possible to some how enable the tsc for this like https://github.com/thomaschaaf/esbuild-plugin-tsc ?

If you really need this, you can switch to ts-node for now. the setup be like **.swcrc** ``` { "$schema": "https://json.schemastore.org/swcrc", "sourceMaps": true, "module": { "type": "es6" }, "jsc": {...

> can ts-node support node V20? Yes > ERR_PACKAGE_PATH_NOT_EXPORTED you should check the import path