v8.0.0

Changes:

DB layer

• DB plugin server methods take an object as the only parameter now for easier extensibility
• A session object with users credentials gets passed into the DB abstraction server methods for a custom implementation to distinguish storage by user (used at livingdocs)
• This is breaking, the calls to these server methods have to be adapted

renderingInfo flow improvements

• this refactors the rendering info flow to handle different types of rendering info more explicitly
• the configurations for targets and toolEndpoints get validated on plugin registration
• it exposes a new endpoint /export-options-schema that combines the display-options-schema from the tool and any export options defined in server configs. This is used for the new export feature in Q-editor: https://github.com/nzzdev/Q-editor/tree/feat-exportable-targets
• if keepMeta: true is set on a toolEndpoint configuration is set, the meta properties are not stripped before the item is sent to the endpoint. This can be used for meta toolEndpoint handlers that still need to know the tool.
• a new configuration option in target or toolEndpoint named processRenderingInfo is handled. It is an array of functions or one function:

({item, toolRuntimeConfig, renderingInfo}) => {
   // change renderingInfo in whatever way you want
  return renderingInfo;
}