@teamkeel/functions-runtime 0.365.13 → 0.365.15-prerelease1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/package.json +1 -1
  2. package/src/tryExecuteJob.js +1 -3
  3. package/pnpm-lock.yaml +0 -1524
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@teamkeel/functions-runtime",
3
- "version": "0.365.13",
3
+ "version": "0.365.15-prerelease1",
4
4
  "description": "Internal package used by @teamkeel/sdk",
5
5
  "main": "src/index.js",
6
6
  "scripts": {
package/src/tryExecuteJob.js CHANGED
@@ -12,9 +12,7 @@ function tryExecuteJob({ db, permitted, actionType, request }, cb) {
12
12
  return withDatabase(db, actionType, async ({ transaction }) => {
13
13
  await cb();
14
14
 
15
- // api.permissions maintains an internal state of whether the current operation has been *explicitly* permitted/denied by the user in the course of their custom function, or if execution has already been permitted by a role based permission (evaluated in the main runtime).
16
- // we need to check that the final state is permitted or unpermitted. if it's not, then it means that the user has taken no explicit action to permit/deny
17
- // and therefore we default to checking the permissions defined in the schema automatically.
15
+ // we need to check that the final state is unpermitted. if it's not, then it means that the user has taken no explicit action to permit/deny
18
16
  if (getPermissionState() === PERMISSION_STATE.UNPERMITTED) {
19
17
  throw new PermissionError(`Not permitted to access ${request.method}`);
20
18
  }