cedar-policy/cedar

Reserve `Set`, `Record`, `Entity`, `Extension` in schemas

Closed this issue · 0 comments

Category

Cedar language or syntax features/changes

Describe the feature you'd like to request

#974 (which is unreleased on the main branch) allowed Set, Record, Entity, and Extension to be common type names. At the time, this seemed like a good change because it removed restrictions on the JSON schema format and made it consistent with the human-readable format. We have since discovered that this will make things difficult for tools that manipulate/generate the JSON format. And, in hindsight, these common type names are likely to lead to confusion anyways.

So this issue proposes to roll back this change in the JSON format, and reserve these keywords in human-readable schema format to match.

Describe alternatives you've considered

No response

Additional context

No response

Is this something that you'd be interested in working on?

  • 👋 I may be able to implement this feature request
  • ⚠️ This feature might incur a breaking change