You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Clients that want to display an icon to visualize a share role currently have to hardcode a table that maps role UUIDs to icon names locally, as can be seen here:
IMO it counters the idea of having share roles returned by the server if clients still have to maintain and ship a list of role UUIDs to be able to "recognize" them and to present them in a visually appealing manner.
Describe the solution you'd like
The UnifiedRoleDefinitions returned by the permissions endpoint should add an extra property that provides hints as to which icon the client should use, like f.ex. eye, pencil, upload, shield.
A standard set of these icon names should be defined, so that clients can map them to local assets.
In order to allow new icons to be added over time, the icon hints should be provided as an array, with clients picking the first icon they know.
In this example the role with ID 1c996275-f1c9-4e71-abdf-a42f6495e960 introduces a new icon, upload-folder that older clients may not yet know. These clients can then fall back to the icon they have stored for upload.
Likewise, the server can introduce new roles and use the existing pool of icon hints - and clients will be able to show an icon for them without the need for source modification or a new release.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Clients that want to display an icon to visualize a share role currently have to hardcode a table that maps role UUIDs to icon names locally, as can be seen here:
IMO it counters the idea of having share roles returned by the server if clients still have to maintain and ship a list of role UUIDs to be able to "recognize" them and to present them in a visually appealing manner.
Describe the solution you'd like
The
UnifiedRoleDefinition
s returned by the permissions endpoint should add an extra property that provides hints as to which icon the client should use, like f.ex.eye
,pencil
,upload
,shield
.A standard set of these icon names should be defined, so that clients can map them to local assets.
In order to allow new icons to be added over time, the icon hints should be provided as an array, with clients picking the first icon they know.
Put together, this could look like this:
In this example the role with ID
1c996275-f1c9-4e71-abdf-a42f6495e960
introduces a new icon,upload-folder
that older clients may not yet know. These clients can then fall back to the icon they have stored forupload
.Likewise, the server can introduce new roles and use the existing pool of icon hints - and clients will be able to show an icon for them without the need for source modification or a new release.
The text was updated successfully, but these errors were encountered: