mirror of
https://github.com/status-im/react-native.git
synced 2025-01-29 10:45:04 +00:00
d5e9e55fa3
Summary: This PR removes the need for having the `providesModule` tags in all the modules in the repository. It configures Flow, Jest and Metro to get the module names from the filenames (`Libraries/Animated/src/nodes/AnimatedInterpolation.js` => `AnimatedInterpolation`) * Checked the Flow configuration by running flow on the project root (no errors): ``` yarn flow ``` * Checked the Jest configuration by running the tests with a clean cache: ``` yarn jest --clearCache && yarn test ``` * Checked the Metro configuration by starting the server with a clean cache and requesting some bundles: ``` yarn run start --reset-cache curl 'localhost:8081/IntegrationTests/AccessibilityManagerTest.bundle?platform=android' curl 'localhost:8081/Libraries/Alert/Alert.bundle?platform=ios' ``` [INTERNAL] [FEATURE] [All] - Removed providesModule from all modules and configured tools. Closes https://github.com/facebook/react-native/pull/18995 Reviewed By: mjesun Differential Revision: D7729509 Pulled By: rubennorte fbshipit-source-id: 892f760a05ce1fddb088ff0cd2e97e521fb8e825
72 lines
2.4 KiB
JavaScript
72 lines
2.4 KiB
JavaScript
/**
|
|
* Copyright (c) 2015-present, Facebook, Inc.
|
|
*
|
|
* This source code is licensed under the MIT license found in the
|
|
* LICENSE file in the root directory of this source tree.
|
|
*
|
|
* @flow
|
|
*/
|
|
'use strict';
|
|
|
|
const NativeModules = require('NativeModules');
|
|
|
|
const invariant = require('fbjs/lib/invariant');
|
|
|
|
/**
|
|
* Flow API for native FrameRateLogger module. If the native module is not installed, function calls
|
|
* are just no-ops.
|
|
*
|
|
* Typical behavior is that `setContext` is called when a new screen is loaded (e.g. via a
|
|
* navigation integration), and then `beginScroll` is called by `ScrollResponder` at which point the
|
|
* native module then begins tracking frame drops. When `ScrollResponder` calls `endScroll`, the
|
|
* native module gathers up all it's frame drop data and reports it via an analytics pipeline for
|
|
* analysis.
|
|
*
|
|
* Note that `beginScroll` may be called multiple times by `ScrollResponder` - unclear if that's a
|
|
* bug, but the native module should be robust to that.
|
|
*
|
|
* In the future we may add support for tracking frame drops in other types of interactions beyond
|
|
* scrolling.
|
|
*/
|
|
const FrameRateLogger = {
|
|
/**
|
|
* Enable `debug` to see local logs of what's going on. `reportStackTraces` will grab stack traces
|
|
* during UI thread stalls and upload them if the native module supports it.
|
|
*/
|
|
setGlobalOptions: function(options: {debug?: boolean, reportStackTraces?: boolean}) {
|
|
if (options.debug !== undefined) {
|
|
invariant(
|
|
NativeModules.FrameRateLogger,
|
|
'Trying to debug FrameRateLogger without the native module!',
|
|
);
|
|
}
|
|
NativeModules.FrameRateLogger && NativeModules.FrameRateLogger.setGlobalOptions(options);
|
|
},
|
|
|
|
/**
|
|
* Must call `setContext` before any events can be properly tracked, which is done automatically
|
|
* in `AppRegistry`, but navigation is also a common place to hook in.
|
|
*/
|
|
setContext: function(context: string) {
|
|
NativeModules.FrameRateLogger && NativeModules.FrameRateLogger.setContext(context);
|
|
},
|
|
|
|
/**
|
|
* Called in `ScrollResponder` so any component that uses that module will handle this
|
|
* automatically.
|
|
*/
|
|
beginScroll() {
|
|
NativeModules.FrameRateLogger && NativeModules.FrameRateLogger.beginScroll();
|
|
},
|
|
|
|
/**
|
|
* Called in `ScrollResponder` so any component that uses that module will handle this
|
|
* automatically.
|
|
*/
|
|
endScroll() {
|
|
NativeModules.FrameRateLogger && NativeModules.FrameRateLogger.endScroll();
|
|
},
|
|
};
|
|
|
|
module.exports = FrameRateLogger;
|