Resource types are bound to application ids, i.e. their first part needs to match an existing application id and they can only be edited by members of the team who owns the referenced application. However, prior to this logic, it was possible to create resource types with arbitrary names and they are still in our database. Unfortunately they can't be edited by users, because the a reference to the application cannot be established.
It would be nice if in those cases a message would be displayed to the user. Something similar to:
"This resource type is deprecated – scopes will continue to work, but no new ones can be created."
Resource types are bound to application ids, i.e. their first part needs to match an existing application id and they can only be edited by members of the team who owns the referenced application. However, prior to this logic, it was possible to create resource types with arbitrary names and they are still in our database. Unfortunately they can't be edited by users, because the a reference to the application cannot be established.
It would be nice if in those cases a message would be displayed to the user. Something similar to: "This resource type is deprecated – scopes will continue to work, but no new ones can be created."