jitsi_app_c0

Vēsture

Saúl Ibarra Corretgé 4a8f787519 rn: evaluate config.js in a sandboxed environment We are downloading code off the Internet and executing it on the user's device, so run it sandboxed to avoid potential bad actors. Since it's impossible to eval() safely in JS and React Native doesn't offer something akin to Node's vm module, here we are rolling our own. On Android it uses the Duktape JavaScript engine and on iOS the builtin JavaScriptCore engine. The extra JS engine is only used for evaluating the downloaded code and returning a JSON string which is then passed back to RN.		5 gadus atpakaļ
..
native	logging: use individual, names loggers	5 gadus atpakaļ
_.native.js	ref(strophe): Remove and cleanup all strophe related code.	7 gadus atpakaļ
_.web.js	cleanup: drop polyfills which were required for IE11	7 gadus atpakaļ
actionTypes.js	chore: use strings as action types	6 gadus atpakaļ
actions.js	flow: tame the beast	6 gadus atpakaļ
functions.any.js	rn: evaluate config.js in a sandboxed environment	5 gadus atpakaļ
functions.native.js	rn: evaluate config.js in a sandboxed environment	5 gadus atpakaļ
functions.web.js	rn: evaluate config.js in a sandboxed environment	5 gadus atpakaļ
index.js	feat: Displays the E2E RTT in the connection stats table. (#3344)	6 gadus atpakaļ
logger.js	logging: use individual, names loggers	5 gadus atpakaļ
middleware.js	core: refactor routing	7 gadus atpakaļ
reducer.js	core: refactor routing	7 gadus atpakaļ