0af7c7ecbb
Removing the `BridgeQuery.or` API since 1. it reads confusing. Are the passed-in items applied with an `or`, or the current queries applied with the parameters with an `or`. Unlike `and` method, this difference with `or` can change the meaning of the query drastically. 2. it doesn't translate very well into Postgres world. Multiple hoops to manage the same API, just not worth it. The static `Bridge.or` looks, reads, and works much better. That's the suggested alternative for this. |
||
|---|---|---|
| .. | ||
| .run | ||
| appsmith-git | ||
| appsmith-interfaces | ||
| appsmith-plugins | ||
| appsmith-server | ||
| envs | ||
| mongo-seed | ||
| reactive-caching | ||
| scripts | ||
| .gitignore | ||
| build.sh | ||
| buildpack-run.sh | ||
| docker-compose.yml | ||
| pom.xml | ||
| Procfile | ||
| README.md | ||
| system.properties | ||
Appsmith Server
This is the server-side repository for the Appsmith framework.
For details on setting up your development machine, please refer to this Setup Guide.