As a user authoring an authorization model, I want to be able to freely define types and later define its relationships.
Right now we require types to have at least one relation, which is enforced at the API-level.
We could enable types without relationship, which would simplify prototyping, e.g. when asking users to start working on their model, they can start listing the types, saving and then go through them as they update the relations.
We'll need to:
Update the validation logic to allow a single type in the API JSON
Right now we require types to have at least one relation, which is enforced at the API-level.
We could enable types without relationship, which would simplify prototyping, e.g. when asking users to start working on their model, they can start listing the types, saving and then go through them as they update the relations.
We'll need to: