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. |
||
|---|---|---|
| .. | ||
| src | ||
| auth-notes | ||
| pom.xml | ||