7fd55fe27d
* backend for triggering automation based on filters * frontend for handling triggering automations on filter / old row * lint and bug fix * fix issue with test header * make test data optional * improve safety on trigger gate * add support for running trigger with filter if no change happened but filter matches * update var naming to actually make sense * tests * fix lint * improve gating for shouldTrigger check * remove unecessary cast * unecessary tableId check * frontend text updates * resolving comments * pro * Update packages/types/src/documents/app/automation.ts Co-authored-by: Sam Rose <hello@samwho.dev> * link out to docs for trigger filtering * fix pro * more pr comments * use getAppId --------- Co-authored-by: Sam Rose <hello@samwho.dev> |
||
|---|---|---|
| .. | ||
| __mocks__ | ||
| build | ||
| scripts | ||
| specs | ||
| src | ||
| .dockerignore | ||
| .gitignore | ||
| .npmignore | ||
| .yarnrc | ||
| babel.config.js | ||
| docker_run.sh | ||
| Dockerfile | ||
| jest.config.ts | ||
| LICENSE | ||
| nodemon.json | ||
| package.json | ||
| pm2.config.js | ||
| README.md | ||
| tsconfig.build.json | ||
| tsconfig.json | ||
Budibase server project
This project contains all the server specific logic required to run a Budibase app
App migrations
A migration system has been created in order to modify existing apps when breaking changes are added. These migrations will run on the app startup (both from the client side or the builder side), blocking the access until they are correctly applied.
Create a new migration
In order to add a new migration:
- Run
yarn add-app-migration [title] - Write your code on the newly created file