Get configuration data for a key.
Retrieves the configuration value stored under the specified key.
Returns the stored data, or undefined if the key doesn't exist.
Use the type parameter <T> to specify the expected type of the configuration
data for type safety. The repository does not validate types at runtime.
Name of the configuration key to retrieve
The stored configuration data, or undefined if not found
import { PlatformServiceName } from '@limetech/lime-web-components';
interface CompanyCardConfig {
card: {
fields: string[];
};
}
const configs = platform.get(PlatformServiceName.ConfigRepository);
// The type parameter says what the config looks like, it does not promise the
// key exists, so guard the value before using it
const cardConfig = configs.get<CompanyCardConfig>(
'webclient_view.company'
)?.card;
Check if a configuration key exists.
Returns true if configuration data has been stored under the specified key,
false otherwise. Use this to check for the existence of optional configuration
before attempting to retrieve it.
Name of the configuration key to check
true if the configuration exists, false otherwise
import { PlatformServiceName } from '@limetech/lime-web-components';
const configs = platform.get(PlatformServiceName.ConfigRepository);
// Render the built-in columns when no admin has configured any
const hasCustomColumns = configs.has('person_table_columns');
Save configuration data under a key.
Important: This method requires admin privileges. The backend endpoint is protected and will reject requests from non-admin users.
Stores the provided data persistently under the specified key. If the key already exists, its value is overwritten. The data is serialized and saved to the database, making it available to all users across the application.
After saving, the repository state is updated, triggering any subscriptions. The data can be any serializable JavaScript value (objects, arrays, primitives).
Name of the configuration key to set
Configuration data to store (must be serializable)
Promise that resolves when the data is saved
import { PlatformServiceName } from '@limetech/lime-web-components';
interface PluginConfiguration {
enabled: boolean;
apiEndpoint: string;
settings: {
timeout: number;
retries: number;
};
}
const pluginConfig: PluginConfiguration = {
enabled: true,
apiEndpoint: 'https://api.example.com',
settings: {
timeout: 5000,
retries: 3,
},
};
const configs = platform.get(PlatformServiceName.ConfigRepository);
// The backend endpoint rejects this call for anyone who is not an admin
await configs.set('my_plugin_config', pluginConfig);
Subscribe to state changes with optional transformation and filtering.
The subscription will immediately invoke the callback with the current state (if any), then continue to call it whenever the state changes. The map and filter options allow you to transform and selectively receive updates.
Function called with state updates (after map/filter applied)
Optionaloptions: StateOptionsOptional transformations and filters for the subscription
Unsubscribe function - call this to stop receiving updates
import { PlatformServiceName } from '@limetech/lime-web-components';
const repository = platform.get(PlatformServiceName.Application);
const logger = platform
.get(PlatformServiceName.Logger)
.createLogger('my-component');
// Basic subscription
const unsubscribeState = repository.subscribe((state) => {
logger.debug('State updated', { state });
});
// With transformations
const unsubscribeUserName = repository.subscribe(
(userName) => logger.debug('User', { userName }),
{ map: [(state) => state.currentUser?.fullname] }
);
Repository for storing and retrieving application-wide configuration data.
ConfigRepository provides persistent key-value storage for configuration that applies to all users across the application. Typical use cases include:
Each plugin or package typically manages its own configuration namespace, storing settings that define how components should be rendered or behave for all users.
Important: This repository is NOT for user preferences. User-specific settings should use UserPreferencesRepository instead.
Configuration data is:
The repository extends StateRepository, providing reactive state management with automatic UI updates when configuration changes.
Access the repository through the platform service:
Example: Read view configuration
Example: Read plugin configuration with type safety
See
StateRepository for subscription patterns