Browse Source

Fix issue with determining when to hide sensitive fields from query definitions and never delete the query schema

master
Andrew Kingston 5 years ago
parent
commit
737ce9dc32
  1. 9
      packages/server/src/api/controllers/query.js

9
packages/server/src/api/controllers/query.js

@ -1,6 +1,10 @@
const { processString } = require("@budibase/string-templates")
const CouchDB = require("../../db")
const { generateQueryID, getQueryParams } = require("../../db/utils")
const {
generateQueryID,
getQueryParams,
isProdAppID,
} = require("../../db/utils")
const { BaseQueryVerbs } = require("../../constants")
const env = require("../../environment")
const { Thread, ThreadType } = require("../../threads")
@ -90,10 +94,9 @@ exports.find = async function (ctx) {
const db = new CouchDB(ctx.appId)
const query = enrichQueries(await db.get(ctx.params.queryId))
// remove properties that could be dangerous in real app
if (env.isProd()) {
if (isProdAppID(ctx.appId)) {
delete query.fields
delete query.parameters
delete query.schema
}
ctx.body = query
}

Loading…
Cancel
Save