jiti-meet/react/features/base/config/index.js

export * from './actions';
export * from './actionTypes';
export { default as CONFIG_WHITELIST } from './configWhitelist';
export * from './functions';
Introduce features/base/config 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. 2017-04-23 20:14:02 +00:00			`export * from './actions';`
			`export * from './actionTypes';`
fix(settings): respect configWhitelist 2019-11-01 13:24:52 +00:00			`export { default as CONFIG_WHITELIST } from './configWhitelist';`
Create config util 2017-04-21 10:55:08 +00:00			`export * from './functions';`