react/features/base/config/index.js

export * from './actions';
export * from './actionTypes';
export { default as CONFIG_WHITELIST } from './configWhitelist';
export * from './constants';
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 15:14:02 -05: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';`
feat: Update video receiver constraints to use source names (#10527) * feat: Use source name based receiver constraints * add sourceNameSignaling feature flag to config * move source name specific variables into if block * ensure sourceName is defined in constraints * use source name for selectedSources * use selector to find video track by participant id * add selector to encapsulate logic to get track source name * refactor getTrackSourceNameByMediaTypeAndParticipant selector * rename variable * move flags config into Feature Flags section * do not set constraints for local large video * rename prioritizedSources to onStageSources * fix flow error * refactor visibleRemoteTrackSourceNames to a constant * use selector to get feature flags * rename selector function * fix flow error * add selector for sourceNameSignaling feature flag 2021-12-16 12:49:36 -05:00			`export * from './constants';`
Create config util 2017-04-21 13:55:08 +03:00			`export * from './functions';`