leaonline / leaonline-backend Goto Github PK

Settings is not a global route

The router's register function set's on each route the title - currently as function, but it should be the translated string.

We need a collection, that manages settings for all the contexts.

In this settings, we define

• whether we use a history for editing context's documents
• which templates we map to this context
• which fields we display for lists, previews, summaries, forms etc.
• which fields are edited with a specific custom autoform template

The schema should look like the following:

{
  // name of the app that registered to the backend
  app: String,

  // name of the context that has been registered
  name: String,

  // edit log / history flag
  useHistory: Boolean,

  // comments flag
  useComments: Boolean,

  // flag if we want to track links to this context
  useDependencyTracking: Boolean,

  // which template to use as main template for overview
  template: String,

  // define fields-specific settings
  fields: Array
  'fields.$': Object,

  // field name / key (not label)
  'field.$.name': String,

  // may it appear in lists
  'field.$.list': Boolean,

  // may it appear in summaries and previews
  'field.$.summary': Boolean,

  // is there a specific autoform formType to use 
  'field.$.formType': Boolean,
}

• The ContextSettings should only be editable by an admin account. Later we should define ways for editors to override certain settings (for instance which fields to display in lists etc.)
• When no settings exist for a certain context, then load first the settings form page.