This is because this `cacheResponse` field is only used for auto-complete on the UI. The user can still run the action manually and get the auto-complete to work. The downside to sending the `cacheResponse` field in the JSON response is that for large responses, the client times out as our response times increase to 20 secs. Hence removing this for now. In future, we'll extract the JSON schema structure from the response body and send that to the client for populating auto-complete. |
||
|---|---|---|
| .. | ||
| appsmith-interfaces | ||
| appsmith-plugins | ||
| appsmith-server | ||
| envs | ||
| mongo-seed | ||
| scripts | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| build.sh | ||
| buildpack-run.sh | ||
| docker-compose.yml | ||
| Dockerfile | ||
| entrypoint.sh | ||
| pom.xml | ||
| Procfile | ||
| README.md | ||
| system.properties | ||
Appsmith Server
This is the server-side repo for the Appsmith framework.
How to build
$ ./build.sh <arguments>
For example:
$ ./build.sh -DskipTests
This script will perform the following steps:
- Compile the code
- Generate the jars for server & plugins
- Copy them into the
distdirectory
How to run
$ cd ./dist
$ java -jar -Dspring.profiles.active=$env server-1.0-SNAPSHOT.jar
How to test
In order to test the code, you can run the following command
mvn -B clean package
Please make sure that you have a local Redis instance running for the test cases. The MongoDB is run in-memory during tests so that shouldn't be a problem.