mirror of
https://gitcode.com/GitHub_Trending/ji/jitsi-meet.git
synced 2026-05-14 03:42:30 +00:00
92e765ea21
The config object defined by lib-jitsi-meet is not used by lib-jitsi-meet only, jitsi-meet respects its values as well. Moreover, jitsi-meet defined classes and/or functions which manipulate that config object. Consequently, it makes sense to move the config object and the associated classes and functions in a dedicated feature.
23 lines
562 B
JavaScript
23 lines
562 B
JavaScript
/* @flow */
|
|
|
|
import { SET_CONFIG } from './actionTypes';
|
|
|
|
/**
|
|
* Sets the configuration represented by the feature base/config. The
|
|
* configuration is defined and consumed by the library lib-jitsi-meet but some
|
|
* of its properties are consumed by the application jitsi-meet as well.
|
|
*
|
|
* @param {Object} config - The configuration to be represented by the feature
|
|
* base/config.
|
|
* @returns {{
|
|
* type: SET_CONFIG,
|
|
* config: Object
|
|
* }}
|
|
*/
|
|
export function setConfig(config: Object) {
|
|
return {
|
|
type: SET_CONFIG,
|
|
config
|
|
};
|
|
}
|