react-native/Libraries/Text/TextAncestor.js

/**
 * 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 strict
 * @format
 */

'use strict';

const React = require('React');

/**
 * Whether the current element is the descendant of a <Text> element.
 */
module.exports = React.createContext(false);
Generalization of `isInAParentText` context Summary: Currently `isInAParentText` context works as imaginary `isInAAncestorText` context (not like a real `isInAParentText`). Let's imagine we have hierarchy like: `View -> Text -> Text* -> View* -> Text* -> Text* -> View` With current implementation all nodes marked with asterisk have `isInAParentText` context, which is incorrect (because some of them actually in View context). With the new implemetations it will work like this: `View -> Text -> Text -> View* -> Text -> Text* -> View*` So, only nodes which have <Text> (or <TextInput>) as a parent will have `isInAParentText` context. This change allows to select proper `Text` vs. `VirtualText` component in cases where <Text> and <View> components can interleave each other. Reviewed By: sahrens Differential Revision: D6690495 fbshipit-source-id: f7c59b23d0eaf68a1d08036b858d99c9547f7878 2018-01-14 19:32:33 -08:00			`/**`
			`* Copyright (c) 2015-present, Facebook, Inc.`
			`*`
Update license headers for MIT license Summary: Includes React Native and its dependencies Fresco, Metro, and Yoga. Excludes samples/examples/docs. find: ^(?:( )\|( (?:[\~#]\|::))( )? )?Copyright (?:\(c\) )?(\d{4})\b.+Facebook[\s\S]+?BSD[\s\S]+?(?:this source tree\|the same directory)\.$ replace: $1$2$3Copyright (c) $4-present, Facebook, Inc.\n$2\n$1$2$3This source code is licensed under the MIT license found in the\n$1$2$3LICENSE file in the root directory of this source tree. Reviewed By: TheSavior, yungsters Differential Revision: D7007050 fbshipit-source-id: 37dd6bf0ffec0923bfc99c260bb330683f35553e 2018-02-16 18:24:55 -08:00			`* This source code is licensed under the MIT license found in the`
			`* LICENSE file in the root directory of this source tree.`
Generalization of `isInAParentText` context Summary: Currently `isInAParentText` context works as imaginary `isInAAncestorText` context (not like a real `isInAParentText`). Let's imagine we have hierarchy like: `View -> Text -> Text* -> View* -> Text* -> Text* -> View` With current implementation all nodes marked with asterisk have `isInAParentText` context, which is incorrect (because some of them actually in View context). With the new implemetations it will work like this: `View -> Text -> Text -> View* -> Text -> Text* -> View*` So, only nodes which have <Text> (or <TextInput>) as a parent will have `isInAParentText` context. This change allows to select proper `Text` vs. `VirtualText` component in cases where <Text> and <View> components can interleave each other. Reviewed By: sahrens Differential Revision: D6690495 fbshipit-source-id: f7c59b23d0eaf68a1d08036b858d99c9547f7878 2018-01-14 19:32:33 -08:00			`*`
Flow strictify possible files in RN core Summary: This was done by running the command on: https://our.intern.facebook.com/intern/wiki/Flow_Strict/ ``` ag -L --ignore __snapshots__ 'flow strict$\|noflow\|generated\|partially-generated' \| ag '\.js$' \| xargs ag -l 'flow' \| sort > ~/temp cat ~/temp \| xargs ag -L 'flow strict' \| xargs sed -i 's/flow$/flow strict/' cat ~/temp \| xargs ag -L 'flow strict$' \| xargs sed -i 's/flow strict-local$/flow strict/' until flow; do flow --json \| jq -r '.errors[].message[0].path' \| sort \| uniq \| xargs hg revert; done ``` Reviewed By: sahrens Differential Revision: D8530207 fbshipit-source-id: c28c7ac5ed3e9b80f3d126d5f30463be8a8a744d 2018-06-20 00:35:29 -07:00			`* @flow strict`
Generalization of `isInAParentText` context Summary: Currently `isInAParentText` context works as imaginary `isInAAncestorText` context (not like a real `isInAParentText`). Let's imagine we have hierarchy like: `View -> Text -> Text* -> View* -> Text* -> Text* -> View` With current implementation all nodes marked with asterisk have `isInAParentText` context, which is incorrect (because some of them actually in View context). With the new implemetations it will work like this: `View -> Text -> Text -> View* -> Text -> Text* -> View*` So, only nodes which have <Text> (or <TextInput>) as a parent will have `isInAParentText` context. This change allows to select proper `Text` vs. `VirtualText` component in cases where <Text> and <View> components can interleave each other. Reviewed By: sahrens Differential Revision: D6690495 fbshipit-source-id: f7c59b23d0eaf68a1d08036b858d99c9547f7878 2018-01-14 19:32:33 -08:00			`* @format`
			`*/`

RN: Replace `context.isInAParentText` w/ React.createContext Reviewed By: sahrens Differential Revision: D7895382 fbshipit-source-id: 4affcecd147b8e8c506e0d94f223bac3e6dfdf66 2018-05-09 00:47:46 -07:00			`'use strict';`
Generalization of `isInAParentText` context Summary: Currently `isInAParentText` context works as imaginary `isInAAncestorText` context (not like a real `isInAParentText`). Let's imagine we have hierarchy like: `View -> Text -> Text* -> View* -> Text* -> Text* -> View` With current implementation all nodes marked with asterisk have `isInAParentText` context, which is incorrect (because some of them actually in View context). With the new implemetations it will work like this: `View -> Text -> Text -> View* -> Text -> Text* -> View*` So, only nodes which have <Text> (or <TextInput>) as a parent will have `isInAParentText` context. This change allows to select proper `Text` vs. `VirtualText` component in cases where <Text> and <View> components can interleave each other. Reviewed By: sahrens Differential Revision: D6690495 fbshipit-source-id: f7c59b23d0eaf68a1d08036b858d99c9547f7878 2018-01-14 19:32:33 -08:00
RN: Replace `context.isInAParentText` w/ React.createContext Reviewed By: sahrens Differential Revision: D7895382 fbshipit-source-id: 4affcecd147b8e8c506e0d94f223bac3e6dfdf66 2018-05-09 00:47:46 -07:00			`const React = require('React');`
Generalization of `isInAParentText` context Summary: Currently `isInAParentText` context works as imaginary `isInAAncestorText` context (not like a real `isInAParentText`). Let's imagine we have hierarchy like: `View -> Text -> Text* -> View* -> Text* -> Text* -> View` With current implementation all nodes marked with asterisk have `isInAParentText` context, which is incorrect (because some of them actually in View context). With the new implemetations it will work like this: `View -> Text -> Text -> View* -> Text -> Text* -> View*` So, only nodes which have <Text> (or <TextInput>) as a parent will have `isInAParentText` context. This change allows to select proper `Text` vs. `VirtualText` component in cases where <Text> and <View> components can interleave each other. Reviewed By: sahrens Differential Revision: D6690495 fbshipit-source-id: f7c59b23d0eaf68a1d08036b858d99c9547f7878 2018-01-14 19:32:33 -08:00
RN: Replace `context.isInAParentText` w/ React.createContext Reviewed By: sahrens Differential Revision: D7895382 fbshipit-source-id: 4affcecd147b8e8c506e0d94f223bac3e6dfdf66 2018-05-09 00:47:46 -07:00			`/**`
			`* Whether the current element is the descendant of a <Text> element.`
			`*/`
			`module.exports = React.createContext(false);`