官术网_书友最值得收藏!

Type checking with PropTypes

React comes with support for basic type checking. It does not require you to upgrade to TypeScript or another, more advanced solution. To achieve type checking straight away, you can use the prop-types library.

Let's provide type definitions for our HelloBox component from Chapter 1/Example 12:

import PropTypes from 'prop-types';

// ...

HelloBox
.propTypes = {
isExpanded: PropTypes.bool.isRequired,
expandOrCollapse: PropTypes.func.isRequired,
containerStyles: PropTypes.object,
expandedTextStyles: PropTypes.object
};

This way, we force isExpanded to be of the Boolean type (true or false), and expandOrCollapse to be a function. We also let React know about two optional style props (containerStyles and expandedTextStyles). If styles are not provided, we simply return the default styles.

There is also a neat feature to avoid explicit if in the markup—default props. Check it out:

HelloBox.defaultProps = {
containerStyles: styles.container,
expandedTextStyles: styles.text
};

Cool! Now, if containerStyles or expandedTextStyles are be null, then they will get a respective default value. However, if you run your application now, you will notice a little warning:

Warning: Failed prop type: Invalid prop `containerStyles` of type `number` supplied to `HelloBox`, expected `object`.

You may be freaking out right now, but this is correct. This is a nice optimization that has been made by the React Native team that you may not be aware of. It caches the stylesheet and simply sends the cached ID. The following line is returning the number and ID of a stylesheet that represents the styles object that was passed:

styles.container

Hence, we need to adapt our type definitions:

HelloBox.propTypes = {
isExpanded: PropTypes.bool.isRequired,
expandOrCollapse: PropTypes.func.isRequired,
containerStyles: PropTypes.oneOfType([
PropTypes.object,
PropTypes.number

]),
expandedTextStyles: PropTypes.oneOfType([
PropTypes.object,
PropTypes.number

])
};

Now, you can remove explicit if statements in the component markup. It should look more or less like this:

export const HelloBox = ({
isExpanded,
expandOrCollapse,
containerStyles,
expandedTextStyles
}) => (
<View style={containerStyles}>
<HelloText onPress={() => expandOrCollapse()}>...</HelloText>
<HelloText onPress={() => expandOrCollapse()}>...</HelloText>
{
isExpanded &&
<HelloText style={expandedTextStyles}>
...

</HelloText>
}
</View>
);

Good job! We have defined default props and type checks for our component. Please check the full working Example 2 in the src/chapter 2 directory for more details.

Please note that, from now on, all code examples will be split into a few modular source files. All files will be placed under the  ./src directory of the respective example.
For instance, Example 2 is organized in the following way:
  • src
    • HelloBox.js
    • HelloText.js
    • makeExpandable.js
  •  App.js
This structure will evolve as the application grows. In Chapter 10, Managing Dependencies, you will learn how to organize files in big projects with over one million lines of code.
主站蜘蛛池模板: 色达县| 灵川县| 马公市| 资阳市| 廊坊市| 广州市| 迁西县| 沭阳县| 京山县| 吉首市| 库尔勒市| 铜鼓县| 峨边| 关岭| 治多县| 平定县| 呼图壁县| 花莲市| 金塔县| 岑溪市| 舒城县| 徐州市| 静乐县| 麟游县| 克东县| 寻甸| 自治县| 营山县| 潜山县| 太保市| 红河县| 桂林市| 双桥区| 长泰县| 克拉玛依市| 张家川| 桂阳县| 朔州市| 上栗县| 响水县| 黄石市|