I'm wondering about naming for

entityType

for a custom workspace. Example:

typescript
const workspace: ManifestWorkspace = {
  type: "workspace",
  kind : 'routable',
  name: "My Settings Workspace",
  alias: "My.Workspace.Settings",
  api: () => import('./my-settings.context.js'),
  meta: {
    entityType : 'settings'
  }  
};

Using

settings

is quite generic and it's quite likely that his would collide with some other package. Anyone been thinking about this? Should packages prefix the entityType? like

mypackage-settings

,

mp-settings

or similar? Only downside is that entity type is used in the routes.