Parser: OR in traverse not allowed

[zepatrik]

Preflight checklist

• I could not find a solution in the existing issues, docs, nor discussions.
• I agree to follow this project's Code of Conduct.
• I have read and am following this repository's Contribution Guidelines.
• This issue affects my Ory Network project.
• I have joined the Ory Community Slack.
• I am signed up to the Ory Security Patch Newsletter.

Describe the bug

error from 18:88 to 18:90: expected ")", got "||"
        	            	
 16 |     view: (ctx: Context): boolean =>
 17 |       this.related.organization.traverse((o) => o.related.manager.includes(ctx.subject) || o.related.member.includes(ctx.subject)),
    |                                                                                         ^~                                         
 18 |   }

Reproducing the bug

Try parsing

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

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

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

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

Workaround:

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

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

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

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

Relevant log output

No response

Relevant configuration

No response

Version

network

On which operating system are you observing this issue?

Ory Network

In which environment are you deploying?

Ory Network

Additional Context

No response