I seem to be unable to save my permission rules in Ory Cloud. I put together these simple rules to test it, and it refuses to save with an error message stating "Could not save OPL config:: Error: Errors during parsing. See editor for details.". When i view the editor, the highlighted error is on line 28 of my input stating

expected ")", got "||"

. This error is incorrect, the typescript is properly formatted and there is no syntax error. So, I'm confused why this is happening. My input:

import { Namespace, Context } from "@ory/permission-namespace-types"

class Organization implements Namespace {
  related: {
    member: Member[]
    manager: Member[]
  }

  permits = {
    view: (ctx: Context): boolean =>
      this.related.manager.includes(ctx.subject) ||
      this.related.member.includes(ctx.subject),
    edit: (ctx: Context): boolean =>
      this.related.manager.includes(ctx.subject),
  }
}

class Member implements Namespace {
  related: {
    manager: Member[]
    organization: Organization[]
  }

  permits = {
    view: (ctx: Context): boolean =>
      this.related.organization.traverse(
        (o) =>
          o.related.manager.includes(ctx.subject) ||
          o.related.member.includes(ctx.subject)
      ),
    edit: (ctx: Context): boolean =>
      this.related.manager.includes(ctx.subject) ||
      this.related.organization.traverse(
        (o) => o.related.manager.includes(ctx.subject)
      ),
    deactivate: (ctx: Context): boolean =>
      this.related.organization.traverse(
        (o) => o.related.manager.includes(ctx.subject)
      ),
  }
}

I see, we do not yet have support in the parser for what you wrote.

Do i understand correctly then that this is not actually parsing the input as Typescript code?..

it is parsing typescript, but never executing typescript

Okay, good to know 👍 I'd highly recommend putting that somewhere in the documentation, or perhaps documenting what the execution is and is not capable of so that others don't waste the 6 hours I wasted on trying to get this working 😓

sorry to hear that... we hoped that the editor errors would be enough, but good point in general

lol, strangely relevant 😆

haha yeahh, thats what I thought as well 😂