Declarations of which core configuration a member who is not a global admin may read, and which core values are credentials that must never be returned.
These live in a module rather than in an entry point because the metadata is process local. The API and the dashboard are separate processes, each with its own pluginManager instance, and a declaration made in one is invisible to the other. The dashboard serializes the security namespace into every page it renders, so a registration that ran only in api/api.js left omitSecretConfigs() with nothing to omit there, and the stored proxy credentials stayed in the page source of every logged in user.
Both entry points call register() so the two processes agree.
- Description:
Declarations of which core configuration a member who is not a global admin may read, and which core values are credentials that must never be returned.
These live in a module rather than in an entry point because the metadata is process local. The API and the dashboard are separate processes, each with its own pluginManager instance, and a declaration made in one is invisible to the other. The dashboard serializes the security namespace into every page it renders, so a registration that ran only in api/api.js left omitSecretConfigs() with nothing to omit there, and the stored proxy credentials stayed in the page source of every logged in user.
Both entry points call register() so the two processes agree.
- Source:
Methods
(static) register(plugins) → {void}
- Description:
Declare the readable and secret core configuration on a pluginManager instance. Safe to call more than once: both setters merge into the existing declaration.
- Source:
Parameters:
| Name | Type | Description |
|---|---|---|
plugins |
object | the pluginManager instance to declare on |
Returns:
- Type
- void