const element = React.createElement('div', { id: 'login-btn' }, 'Login');

{
  type: 'div',
  props: {
    children: 'Login',
    id: 'login-btn'
  }
}

<div id="login-btn">Login</div>

const Button = ({ onLogin }) => (
  <div id={'login-btn'} onClick={onLogin}>
    Login
  </div>
);

const Button = ({ onLogin }) =>
  React.createElement('div', { id: 'login-btn', onClick: onLogin }, 'Login');

```jsx harmony
class User extends React.Component {
  constructor(props) {
    super(props)

    this.state = {
      message: 'Welcome to React world'
    }
  }

  render() {
    return (
      <div>
        <h1>{this.state.message}</h1>
      </div>
    )
  }
}
```

![state](images/state.jpg)

State is similar to props, but it is private and fully controlled by the component. i.e, It is not accessible to any component other than the one that owns and sets it.

This `reactProp` (or whatever you came up with) name then becomes a property attached to React's native props object which originally already exists on all components created using React library.

**Multi-line comments:**

```jsx harmony
<div>
  {/* Multi-line comments for more than
   one line */}
  {`Welcome ${user}, let's play React`}
</div>

⬆ Back to Top

1. What is the purpose of using super constructor with props argument?¶

   A child class constructor cannot make use of this reference until super() method has been called. The same applies for ES6 sub-classes as well. The main reason of passing props parameter to super() call is to access this.props in your child constructors.

   Passing props:

   class MyComponent extends React.Component {
     constructor(props) {
       super(props);
   
       console.log(this.props); // prints { name: 'John', age: 42 }
     }
   }
   

   Not passing props:

   class MyComponent extends React.Component {
     constructor(props) {
       super();
   
       console.log(this.props); // prints undefined
   
       // but props parameter is still available
       console.log(props); // prints { name: 'John', age: 42 }
     }
   
     render() {
       // no difference outside constructor
       console.log(this.props); // prints { name: 'John', age: 42 }
     }
   }
   

   The above code snippets reveals that this.props is different only within the constructor. It would be the same outside the constructor.

⬆ Back to Top

1. What is reconciliation?¶

   When a component's props or state change, React decides whether an actual DOM update is necessary by comparing the newly returned element with the previously rendered one. When they are not equal, React will update the DOM. This process is called reconciliation.

⬆ Back to Top

1. How to set state with a dynamic key name?¶

   If you are using ES6 or the Babel transpiler to transform your JSX code then you can accomplish this with computed property names.

   handleInputChange(event) {
     this.setState({ [event.target.id]: event.target.value })
   }
   

⬆ Back to Top

1. What would be the common mistake of function being called every time the component renders?¶

   You need to make sure that function is not being called while passing the function as a parameter.

   ```jsx harmony render() { // Wrong: handleClick is called instead of passed as a reference! return {'Click Me'} }

   Instead, pass the function itself without parenthesis:
   
   ```jsx harmony
   render() {
     // Correct: handleClick is passed as a reference!
     return <button onClick={this.handleClick}>{'Click Me'}</button>
   }
   

⬆ Back to Top

1. Is lazy function supports named exports?¶

   No, currently React.lazy function supports default exports only. If you would like to import modules which are named exports, you can create an intermediate module that reexports it as the default. It also ensures that tree shaking keeps working and don’t pull unused components. Let's take a component file which exports multiple named components,

   // MoreComponents.js
   export const SomeComponent = /* ... */;
   export const UnusedComponent = /* ... */;
   

   and reexport MoreComponents.js components in an intermediate file IntermediateComponent.js

   // IntermediateComponent.js
   export { SomeComponent as default } from './MoreComponents.js';
   

   Now you can import the module using lazy function as below,

   import React, { lazy } from 'react';
   const SomeComponent = lazy(() => import('./IntermediateComponent.js'));
   

   ⬆ Back to Top

2. Why React uses className over class attribute?¶

   class is a keyword in JavaScript, and JSX is an extension of JavaScript. That's the principal reason why React uses className instead of class. Pass a string as the className prop.

   jsx harmony render() { return <span className={'menu navigation-menu'}>{'Menu'}</span> }

⬆ Back to Top

1. What are fragments?¶

   It's common pattern in React which is used for a component to return multiple elements. Fragments let you group a list of children without adding extra nodes to the DOM.

   ```jsx harmony render() { return ( ) }

   There is also a _shorter syntax_, but it's not supported in many tools:
   
   ```jsx harmony
   render() {
     return (
       <>
         <ChildA />
         <ChildB />
         <ChildC />
       </>
     )
   }
   

⬆ Back to Top

1. Why fragments are better than container divs?¶

   Below are the list of reasons,

   1. Fragments are a bit faster and use less memory by not creating an extra DOM node. This only has a real benefit on very large and deep trees.
   2. Some CSS mechanisms like Flexbox and CSS Grid have a special parent-child relationships, and adding divs in the middle makes it hard to keep the desired layout.
   3. The DOM Inspector is less cluttered.

⬆ Back to Top

1. What are portals in React?¶

   Portal is a recommended way to render children into a DOM node that exists outside the DOM hierarchy of the parent component.

   ReactDOM.createPortal(child, container);
   

   The first argument is any render-able React child, such as an element, string, or fragment. The second argument is a DOM element.

⬆ Back to Top

1. What are stateless components?¶

   If the behaviour is independent of its state then it can be a stateless component. You can use either a function or a class for creating stateless components. But unless you need to use a lifecycle hook in your components, you should go for function components. There are a lot of benefits if you decide to use function components here; they are easy to write, understand, and test, a little faster, and you can avoid the this keyword altogether.

⬆ Back to Top

1. What are stateful components?¶

   If the behaviour of a component is dependent on the state of the component then it can be termed as stateful component. These stateful components are always class components and have a state that gets initialized in the constructor.

   class App extends Component {
     constructor(props) {
       super(props);
       this.state = { count: 0 };
     }
   
     render() {
       // ...
     }
   }
   

   React 16.8 Update:

   Hooks let you use state and other React features without writing classes.

   The Equivalent Functional Component

    import React, {useState} from 'react';
   
    const App = (props) => {
      const [count, setCount] = useState(0);
   
      return (
        // JSX
      )
    }
   

⬆ Back to Top

1. How to apply validation on props in React?¶

   When the application is running in development mode, React will automatically check all props that we set on components to make sure they have correct type. If the type is incorrect, React will generate warning messages in the console. It's disabled in production mode due to performance impact. The mandatory props are defined with isRequired.

   The set of predefined prop types:

   1. PropTypes.number
   2. PropTypes.string
   3. PropTypes.array
   4. PropTypes.object
   5. PropTypes.func
   6. PropTypes.node
   7. PropTypes.element
   8. PropTypes.bool
   9. PropTypes.symbol
   10. PropTypes.any

   We can define propTypes for User component as below:

   ```jsx harmony import React from 'react'; import PropTypes from 'prop-types';

   class User extends React.Component { static propTypes = { name: PropTypes.string.isRequired, age: PropTypes.number.isRequired, };

   render() { return ( <>

   {Welcome, ${this.props.name}}

   {Age, ${this.props.age}}

   
   ); } }

   **Note:** In React v15.5 _PropTypes_ were moved from `React.PropTypes` to `prop-types` library.
   
   _The Equivalent Functional Component_
   
   ```jsx harmony
   import React from 'react';
   import PropTypes from 'prop-types';
   
   function User() {
     return (
       <>
         <h1>{`Welcome, ${this.props.name}`}</h1>
         <h2>{`Age, ${this.props.age}`}</h2>
       </>
     );
   }
   
   User.propTypes = {
     name: PropTypes.string.isRequired,
     age: PropTypes.number.isRequired,
   };
   

   ⬆ Back to Top

2. What are the advantages of React?¶

   Below are the list of main advantages of React,

   1. Increases the application's performance with Virtual DOM.
   2. JSX makes code easy to read and write.
   3. It renders both on client and server side (SSR).
   4. Easy to integrate with frameworks (Angular, Backbone) since it is only a view library.
   5. Easy to write unit and integration tests with tools such as Jest.

⬆ Back to Top

1. What are the limitations of React?¶

   Apart from the advantages, there are few limitations of React too,

   1. React is just a view library, not a full framework.
   2. There is a learning curve for beginners who are new to web development.
   3. Integrating React into a traditional MVC framework requires some additional configuration.
   4. The code complexity increases with inline templating and JSX.
   5. Too many smaller components leading to over engineering or boilerplate.

⬆ Back to Top

1. What are error boundaries in React v16?¶

   Error boundaries are components that catch JavaScript errors anywhere in their child component tree, log those errors, and display a fallback UI instead of the component tree that crashed.

   A class component becomes an error boundary if it defines a new lifecycle method called componentDidCatch(error, info) or static getDerivedStateFromError():

   ```jsx harmony class ErrorBoundary extends React.Component { constructor(props) { super(props); this.state = { hasError: false }; }

   componentDidCatch(error, info) { // You can also log the error to an error reporting service logErrorToMyService(error, info); }

   static getDerivedStateFromError(error) { // Update state so the next render will show the fallback UI. return { hasError: true }; }

   render() { if (this.state.hasError) { // You can render any custom fallback UI return

   {'Something went wrong.'}

   ; } return this.props.children; } }

   After that use it as a regular component:
   
   ```jsx harmony
   <ErrorBoundary>
     <MyWidget />
   </ErrorBoundary>
   

⬆ Back to Top

1. How error boundaries handled in React v15?¶

   React v15 provided very basic support for error boundaries using unstable_handleError method. It has been renamed to componentDidCatch in React v16.

⬆ Back to Top

1. What are the recommended ways for static type checking?¶

   Normally we use PropTypes library (React.PropTypes moved to a prop-types package since React v15.5) for type checking in the React applications. For large code bases, it is recommended to use static type checkers such as Flow or TypeScript, that perform type checking at compile time and provide auto-completion features.

⬆ Back to Top

1. What is the use of react-dom package?¶

   The react-dom package provides DOM-specific methods that can be used at the top level of your app. Most of the components are not required to use this module. Some of the methods of this package are:

   1. render()
   2. hydrate()
   3. unmountComponentAtNode()
   4. findDOMNode()
   5. createPortal()

⬆ Back to Top

1. What is the purpose of render method of react-dom?¶

   This method is used to render a React element into the DOM in the supplied container and return a reference to the component. If the React element was previously rendered into container, it will perform an update on it and only mutate the DOM as necessary to reflect the latest changes.

   ReactDOM.render(element, container[, callback])
   

   If the optional callback is provided, it will be executed after the component is rendered or updated.

⬆ Back to Top

1. What is ReactDOMServer?¶

   The ReactDOMServer object enables you to render components to static markup (typically used on node server). This object is mainly used for server-side rendering (SSR). The following methods can be used in both the server and browser environments:

   1. renderToString()
   2. renderToStaticMarkup()

   For example, you generally run a Node-based web server like Express, Hapi, or Koa, and you call renderToString to render your root component to a string, which you then send as response.

   // using Express
   import { renderToString } from 'react-dom/server';
   import MyPage from './MyPage';
   
   app.get('/', (req, res) => {
     res.write(
       '<!DOCTYPE html><html><head><title>My Page</title></head><body>'
     );
     res.write('<div id="content">');
     res.write(renderToString(<MyPage />));
     res.write('</div></body></html>');
     res.end();
   });
   

⬆ Back to Top

1. How to use innerHTML in React?¶

   The dangerouslySetInnerHTML attribute is React's replacement for using innerHTML in the browser DOM. Just like innerHTML, it is risky to use this attribute considering cross-site scripting (XSS) attacks. You just need to pass a __html object as key and HTML text as value.

   In this example MyComponent uses dangerouslySetInnerHTML attribute for setting HTML markup:

   ```jsx harmony function createMarkup() { return { __html: 'First · Second' }; }

   function MyComponent() { return

   ; } ```

⬆ Back to Top

1. How to use styles in React?¶

   The style attribute accepts a JavaScript object with camelCased properties rather than a CSS string. This is consistent with the DOM style JavaScript property, is more efficient, and prevents XSS security holes.

   ```jsx harmony const divStyle = { color: 'blue', backgroundImage: 'url(' + imgUrl + ')', };

   function HelloWorldComponent() { return

   Hello World!
   ; } ```

   Style keys are camelCased in order to be consistent with accessing the properties on DOM nodes in JavaScript (e.g. node.style.backgroundImage).

⬆ Back to Top

1. How events are different in React?¶

   Handling events in React elements has some syntactic differences:

   1. React event handlers are named using camelCase, rather than lowercase.
   2. With JSX you pass a function as the event handler, rather than a string.

⬆ Back to Top

1. What will happen if you use setState() in constructor?¶

   When you use setState(), then apart from assigning to the object state React also re-renders the component and all its children. You would get error like this: Can only update a mounted or mounting component. So we need to use this.state to initialize variables inside constructor.

⬆ Back to Top

1. What is the impact of indexes as keys?¶

   Keys should be stable, predictable, and unique so that React can keep track of elements.

   In the below code snippet each element's key will be based on ordering, rather than tied to the data that is being represented. This limits the optimizations that React can do.

   ```jsx harmony { todos.map((todo, index) => ); }

   If you use element data for unique key, assuming todo.id is unique to this list and stable, React would be able to reorder elements without needing to reevaluate them as much.
   
   ```jsx harmony
   {
     todos.map(todo => <Todo {...todo} key={todo.id} />);
   }
   

⬆ Back to Top

1. Is it good to use setState() in componentWillMount() method?¶

   Yes, it is safe to use setState() inside componentWillMount() method. But at the same it is recommended to avoid async initialization in componentWillMount() lifecycle method. componentWillMount() is invoked immediately before mounting occurs. It is called before render(), therefore setting state in this method will not trigger a re-render. Avoid introducing any side-effects or subscriptions in this method. We need to make sure async calls for component initialization happened in componentDidMount() instead of componentWillMount().

   jsx harmony componentDidMount() { axios.get(`api/todos`) .then((result) => { this.setState({ messages: [...result.data] }) }) }

⬆ Back to Top

1. What will happen if you use props in initial state?¶

   If the props on the component are changed without the component being refreshed, the new prop value will never be displayed because the constructor function will never update the current state of the component. The initialization of state from props only runs when the component is first created.

   The below component won't display the updated input value:

   ```jsx harmony class MyComponent extends React.Component { constructor(props) { super(props);

   this.state = {
     records: [],
     inputValue: this.props.inputValue,
   };
   

   }

   render() { return

   {this.state.inputValue}
   ; } }

   Using props inside render method will update the value:
   
   ```jsx harmony
   class MyComponent extends React.Component {
     constructor(props) {
       super(props);
   
       this.state = {
         record: [],
       };
     }
   
     render() {
       return <div>{this.props.inputValue}</div>;
     }
   }
   

⬆ Back to Top

1. How do you conditionally render components?¶

   In some cases you want to render different components depending on some state. JSX does not render false or undefined, so you can use conditional short-circuiting to render a given part of your component only if a certain condition is true.

   ```jsx harmony const MyComponent = ({ name, address }) => (

   {name}

   {address &&

   {address}

   }
   );

   If you need an `if-else` condition then use _ternary operator_.
   
   ```jsx harmony
   const MyComponent = ({ name, address }) => (
     <div>
       <h2>{name}</h2>
       {address ? <p>{address}</p> : <p>{'Address is not available'}</p>}
     </div>
   );
   

⬆ Back to Top

1. Why we need to be careful when spreading props on DOM elements?¶

   When we spread props we run into the risk of adding unknown HTML attributes, which is a bad practice. Instead we can use prop destructuring with ...rest operator, so it will add only required props.

   For example,

   ```jsx harmony const ComponentA = () => ( );

   const ComponentB = ({ isDisplay, ...domProps }) => (

   {'ComponentB'}
   ); ```

⬆ Back to Top

1. How you use decorators in React?¶

   You can decorate your class components, which is the same as passing the component into a function. Decorators are flexible and readable way of modifying component functionality.

   ```jsx harmony @setTitle('Profile') class Profile extends React.Component { //.... }

   /* title is a string that will be set as a document title WrappedComponent is what our decorator will receive when put directly above a component class as seen in the example above */ const setTitle = title => WrappedComponent => { return class extends React.Component { componentDidMount() { document.title = title; }

   render() {
     return <WrappedComponent {...this.props} />;
   }
   

   }; }; ```

   Note: Decorators are a feature that didn't make it into ES7, but are currently a stage 2 proposal.

⬆ Back to Top

1. How do you memoize a component?¶

   There are memoize libraries available which can be used on function components.

   For example moize library can memoize the component in another component.

   ```jsx harmony import moize from 'moize'; import Component from './components/Component'; // this module exports a non-memoized component

   const MemoizedFoo = moize.react(Component);

   const Consumer = () => {

   {'I will memoize the following entry:'}
   ; };

   **Update:** Since React v16.6.0, we have a `React.memo`. It provides a higher order component which memoizes component unless the props change. To use it, simply wrap the component using React.memo before you use it.
   
   ```js
   const MemoComponent = React.memo(function MemoComponent(props) {
     /* render using props */
   });
   OR;
   export default React.memo(MyFunctionComponent);
   

   ⬆ Back to Top

2. How you implement Server Side Rendering or SSR?¶

   React is already equipped to handle rendering on Node servers. A special version of the DOM renderer is available, which follows the same pattern as on the client side.

   ```jsx harmony import ReactDOMServer from 'react-dom/server'; import App from './App';

   ReactDOMServer.renderToString(); ```

   This method will output the regular HTML as a string, which can be then placed inside a page body as part of the server response. On the client side, React detects the pre-rendered content and seamlessly picks up where it left off.

⬆ Back to Top

1. How to enable production mode in React?¶

   You should use Webpack's DefinePlugin method to set NODE_ENV to production, by which it strip out things like propType validation and extra warnings. Apart from this, if you minify the code, for example, Uglify's dead-code elimination to strip out development only code and comments, it will drastically reduce the size of your bundle.

⬆ Back to Top

1. What is CRA and its benefits?¶

   The create-react-app CLI tool allows you to quickly create & run React applications with no configuration step.

   Let's create Todo App using CRA:

   # Installation
   $ npm install -g create-react-app
   
   # Create new project
   $ create-react-app todo-app
   $ cd todo-app
   
   # Build, test and run
   $ npm run build
   $ npm run test
   $ npm start
   

   It includes everything we need to build a React app:

   1. React, JSX, ES6, and Flow syntax support.
   2. Language extras beyond ES6 like the object spread operator.
   3. Autoprefixed CSS, so you don’t need -webkit- or other prefixes.
   4. A fast interactive unit test runner with built-in support for coverage reporting.
   5. A live development server that warns about common mistakes.
   6. A build script to bundle JS, CSS, and images for production, with hashes and sourcemaps.

⬆ Back to Top

1. What is the lifecycle methods order in mounting?¶

   The lifecycle methods are called in the following order when an instance of a component is being created and inserted into the DOM.

   1. constructor()
   2. static getDerivedStateFromProps()
   3. render()
   4. componentDidMount()

⬆ Back to Top

1. What are the lifecycle methods going to be deprecated in React v16?¶

   The following lifecycle methods going to be unsafe coding practices and will be more problematic with async rendering.

   1. componentWillMount()
   2. componentWillReceiveProps()
   3. componentWillUpdate()

   Starting with React v16.3 these methods are aliased with UNSAFE_ prefix, and the unprefixed version will be removed in React v17.

⬆ Back to Top

1. What is the purpose of getDerivedStateFromProps() lifecycle method?¶

   The new static getDerivedStateFromProps() lifecycle method is invoked after a component is instantiated as well as before it is re-rendered. It can return an object to update state, or null to indicate that the new props do not require any state updates.

   class MyComponent extends React.Component {
     static getDerivedStateFromProps(props, state) {
       // ...
     }
   }
   

   This lifecycle method along with componentDidUpdate() covers all the use cases of componentWillReceiveProps().

⬆ Back to Top

1. What is the purpose of getSnapshotBeforeUpdate() lifecycle method?¶

   The new getSnapshotBeforeUpdate() lifecycle method is called right before DOM updates. The return value from this method will be passed as the third parameter to componentDidUpdate().

   class MyComponent extends React.Component {
     getSnapshotBeforeUpdate(prevProps, prevState) {
       // ...
     }
   }
   

   This lifecycle method along with componentDidUpdate() covers all the use cases of componentWillUpdate().

⬆ Back to Top

1. Do Hooks replace render props and higher order components?¶

   Both render props and higher-order components render only a single child but in most of the cases Hooks are a simpler way to serve this by reducing nesting in your tree.

⬆ Back to Top

1. What is the recommended way for naming components?¶

   It is recommended to name the component by reference instead of using displayName.

   Using displayName for naming component:

   export default React.createClass({
     displayName: 'TodoApp',
     // ...
   });
   

   The recommended approach:

   export default class TodoApp extends React.Component {
     // ...
   }
   

⬆ Back to Top

1. What is the recommended ordering of methods in component class?¶

   Recommended ordering of methods from mounting to render stage:

   1. static methods
   2. constructor()
   3. getChildContext()
   4. componentWillMount()
   5. componentDidMount()
   6. componentWillReceiveProps()
   7. shouldComponentUpdate()
   8. componentWillUpdate()
   9. componentDidUpdate()
   10. componentWillUnmount()
   11. click handlers or event handlers like onClickSubmit() or onChangeDescription()
   12. getter methods for render like getSelectReason() or getFooterContent()
   13. optional render methods like renderNavigation() or renderProfilePicture()
   14. render()

⬆ Back to Top

1. What is a switching component?¶

   A switching component is a component that renders one of many components. We need to use object to map prop values to components.

   For example, a switching component to display different pages based on page prop:

   ```jsx harmony import HomePage from './HomePage'; import AboutPage from './AboutPage'; import ServicesPage from './ServicesPage'; import ContactPage from './ContactPage';

   const PAGES = { home: HomePage, about: AboutPage, services: ServicesPage, contact: ContactPage, };

   const Page = props => { const Handler = PAGES[props.page] || ContactPage;

   return ; };

   // The keys of the PAGES object can be used in the prop types to catch dev-time errors. Page.propTypes = { page: PropTypes.oneOf(Object.keys(PAGES)).isRequired, }; ```

⬆ Back to Top

1. Why we need to pass a function to setState()?¶

   The reason behind for this is that setState() is an asynchronous operation. React batches state changes for performance reasons, so the state may not change immediately after setState() is called. That means you should not rely on the current state when calling setState() since you can't be sure what that state will be. The solution is to pass a function to setState(), with the previous state as an argument. By doing this you can avoid issues with the user getting the old state value on access due to the asynchronous nature of setState().

   Let's say the initial count value is zero. After three consecutive increment operations, the value is going to be incremented only by one.

   // assuming this.state.count === 0
   this.setState({ count: this.state.count + 1 });
   this.setState({ count: this.state.count + 1 });
   this.setState({ count: this.state.count + 1 });
   // this.state.count === 1, not 3
   

   If we pass a function to setState(), the count gets incremented correctly.

   this.setState((prevState, props) => ({
     count: prevState.count + props.increment,
   }));
   // this.state.count === 3 as expected
   

   (OR)

   Why function is preferred over object for setState()?¶

   React may batch multiple setState() calls into a single update for performance. Because this.props and this.state may be updated asynchronously, you should not rely on their values for calculating the next state.

   This counter example will fail to update as expected:

   // Wrong
   this.setState({
     counter: this.state.counter + this.props.increment,
   });
   

   The preferred approach is to call setState() with function rather than object. That function will receive the previous state as the first argument, and the props at the time the update is applied as the second argument.

   // Correct
   this.setState((prevState, props) => ({
     counter: prevState.counter + props.increment,
   }));
   

⬆ Back to Top

1. What is strict mode in React?¶

   React.StrictMode is a useful component for highlighting potential problems in an application. Just like <Fragment>, <StrictMode> does not render any extra DOM elements. It activates additional checks and warnings for its descendants. These checks apply for development mode only.

   ```jsx harmony import React from 'react';

   function ExampleApplication() { return (

   ); } ```

   In the example above, the strict mode checks apply to <ComponentOne> and <ComponentTwo> components only.

⬆ Back to Top

1. What are React Mixins?¶

   Mixins are a way to totally separate components to have a common functionality. Mixins should not be used and can be replaced with higher-order components or decorators.

   One of the most commonly used mixins is PureRenderMixin. You might be using it in some components to prevent unnecessary re-renders when the props and state are shallowly equal to the previous props and state:

   const PureRenderMixin = require('react-addons-pure-render-mixin');
   
   const Button = React.createClass({
     mixins: [PureRenderMixin],
     // ...
   });
   

⬆ Back to Top

1. Why is isMounted() an anti-pattern and what is the proper solution?¶

   The primary use case for isMounted() is to avoid calling setState() after a component has been unmounted, because it will emit a warning.

   if (this.isMounted()) {
     this.setState({...})
   }
   

   Checking isMounted() before calling setState() does eliminate the warning, but it also defeats the purpose of the warning. Using isMounted() is a code smell because the only reason you would check is because you think you might be holding a reference after the component has unmounted.

   An optimal solution would be to find places where setState() might be called after a component has unmounted, and fix them. Such situations most commonly occur due to callbacks, when a component is waiting for some data and gets unmounted before the data arrives. Ideally, any callbacks should be canceled in componentWillUnmount(), prior to unmounting.

⬆ Back to Top

1. What are the Pointer Events supported in React?¶

   Pointer Events provide a unified way of handling all input events. In the old days we had a mouse and respective event listeners to handle them but nowadays we have many devices which don't correlate to having a mouse, like phones with touch surface or pens. We need to remember that these events will only work in browsers that support the Pointer Events specification.

   The following event types are now available in React DOM:

   1. onPointerDown
   2. onPointerMove
   3. onPointerUp
   4. onPointerCancel
   5. onGotPointerCapture
   6. onLostPointerCapture
   7. onPointerEnter
   8. onPointerLeave
   9. onPointerOver
   10. onPointerOut

⬆ Back to Top

1. Why should component names start with capital letter?¶

   If you are rendering your component using JSX, the name of that component has to begin with a capital letter otherwise React will throw an error as unrecognized tag. This convention is because only HTML elements and SVG tags can begin with a lowercase letter.

   ```jsx harmony class SomeComponent extends Component { // Code goes here }

   You can define component class which name starts with lowercase letter, but when it's imported it should have capital letter. Here lowercase is fine:
   
   ```jsx harmony
   class myComponent extends Component {
     render() {
       return <div />;
     }
   }
   
   export default myComponent;
   

   While when imported in another file it should start with capital letter:

   jsx harmony import MyComponent from './MyComponent';

What are the exceptions on React component naming?¶

 The component names should start with a uppercase letter but there are few exceptions on this convention. The lowercase tag names with a dot (property accessors) are still considered as valid component names.

 For example the below tag can be compiled to a valid component,

 ```jsx harmony
 render(){
    return (
        <obj.component /> // `React.createElement(obj.component)`
       )
 }
 ```

⬆ Back to Top

1. Are custom DOM attributes supported in React v16?¶

   Yes. In the past, React used to ignore unknown DOM attributes. If you wrote JSX with an attribute that React doesn't recognize, React would just skip it.

   For example, let's take a look at the below attribute:

   ```jsx harmony

   Would render an empty div to the DOM with React v15:
   
   ```html
   <div />
   

   In React v16 any unknown attributes will end up in the DOM:

   <div mycustomattribute="something" />
   

   This is useful for supplying browser-specific non-standard attributes, trying new DOM APIs, and integrating with opinionated third-party libraries.

⬆ Back to Top

1. What is the difference between constructor and getInitialState?¶

   You should initialize state in the constructor when using ES6 classes, and getInitialState() method when using React.createClass().

   Using ES6 classes:

   class MyComponent extends React.Component {
     constructor(props) {
       super(props);
       this.state = {
         /* initial state */
       };
     }
   }
   

   Using React.createClass():

   const MyComponent = React.createClass({
     getInitialState() {
       return {
         /* initial state */
       };
     },
   });
   

   Note: React.createClass() is deprecated and removed in React v16. Use plain JavaScript classes instead.

⬆ Back to Top

1. Can you force a component to re-render without calling setState?¶

   By default, when your component's state or props change, your component will re-render. If your render() method depends on some other data, you can tell React that the component needs re-rendering by calling forceUpdate().

   component.forceUpdate(callback);
   

   It is recommended to avoid all uses of forceUpdate() and only read from this.props and this.state in render().

⬆ Back to Top

1. What is the difference between super() and super(props) in React using ES6 classes?¶

   When you want to access this.props in constructor() then you should pass props to super() method.

   Using super(props):

   class MyComponent extends React.Component {
     constructor(props) {
       super(props);
       console.log(this.props); // { name: 'John', ... }
     }
   }
   

   Using super():

   class MyComponent extends React.Component {
     constructor(props) {
       super();
       console.log(this.props); // undefined
     }
   }
   

   Outside constructor() both will display same value for this.props.

⬆ Back to Top

1. How to loop inside JSX?¶

   You can simply use Array.prototype.map with ES6 arrow function syntax.

   For example, the items array of objects is mapped into an array of components:

   ```jsx harmony {items.map(item => ( ))}

   But you can't iterate using `for` loop:
   
   ```jsx harmony
   <tbody>
     for (let i = 0; i < items.length; i++) {
       <SomeComponent key={items[i].id} name={items[i].name} />
     }
   </tbody>
   

   This is because JSX tags are transpiled into function calls, and you can't use statements inside expressions. This may change thanks to do expressions which are stage 1 proposal.

⬆ Back to Top

1. How do you access props in attribute quotes?¶

   React (or JSX) doesn't support variable interpolation inside an attribute value. The below representation won't work:

   ```jsx harmony

   But you can put any JS expression inside curly braces as the entire attribute value. So the below expression works:
   
   ```jsx harmony
   <img className="image" src={'images/' + this.props.image} />
   

   Using template strings will also work:

   jsx harmony <img className="image" src={`images/${this.props.image}`} />

⬆ Back to Top

1. What is React proptype array with shape?¶

   If you want to pass an array of objects to a component with a particular shape then use React.PropTypes.shape() as an argument to React.PropTypes.arrayOf().

   ReactComponent.propTypes = {
     arrayWithShape: React.PropTypes.arrayOf(
       React.PropTypes.shape({
         color: React.PropTypes.string.isRequired,
         fontSize: React.PropTypes.number.isRequired,
       })
     ).isRequired,
   };
   

⬆ Back to Top

1. How to conditionally apply class attributes?¶

   You shouldn't use curly braces inside quotes because it is going to be evaluated as a string.

   ```jsx harmony

   Instead you need to move curly braces outside (don't forget to include spaces between class names):
   
   ```jsx harmony
   <div className={'btn-panel ' + (this.props.visible ? 'show' : 'hidden')}>
   

   Template strings will also work:

   jsx harmony <div className={`btn-panel ${this.props.visible ? 'show' : 'hidden'}`}>

⬆ Back to Top

1. What is the difference between React and ReactDOM?¶

   The react package contains React.createElement(), React.Component, React.Children, and other helpers related to elements and component classes. You can think of these as the isomorphic or universal helpers that you need to build components. The react-dom package contains ReactDOM.render(), and in react-dom/server we have server-side rendering support with ReactDOMServer.renderToString() and ReactDOMServer.renderToStaticMarkup().

⬆ Back to Top

1. Why ReactDOM is separated from React?¶

   The React team worked on extracting all DOM-related features into a separate library called ReactDOM. React v0.14 is the first release in which the libraries are split. By looking at some of the packages, react-native, react-art, react-canvas, and react-three, it has become clear that the beauty and essence of React has nothing to do with browsers or the DOM.

   To build more environments that React can render to, React team planned to split the main React package into two: react and react-dom. This paves the way to writing components that can be shared between the web version of React and React Native.

⬆ Back to Top

1. How to use React label element?¶

   If you try to render a <label> element bound to a text input using the standard for attribute, then it produces HTML missing that attribute and prints a warning to the console.

   ```jsx harmony {'User'}

   Since `for` is a reserved keyword in JavaScript, use `htmlFor` instead.
   
   ```jsx harmony
   <label htmlFor={'user'}>{'User'}</label>
   <input type={'text'} id={'user'} />
   

⬆ Back to Top

1. How to combine multiple inline style objects?¶

   You can use spread operator in regular React:

   ```jsx harmony {'Submit'}

   If you're using React Native then you can use the array notation:
   
   ```jsx harmony
   <button style={[styles.panel.button, styles.panel.submitButton]}>
     {'Submit'}
   </button>
   

⬆ Back to Top

1. How to re-render the view when the browser is resized?¶

   You can listen to the resize event in componentDidMount() and then update the dimensions (width and height). You should remove the listener in componentWillUnmount() method.

   class WindowDimensions extends React.Component {
     constructor(props) {
       super(props);
       this.updateDimensions = this.updateDimensions.bind(this);
     }
   
     componentWillMount() {
       this.updateDimensions();
     }
   
     componentDidMount() {
       window.addEventListener('resize', this.updateDimensions);
     }
   
     componentWillUnmount() {
       window.removeEventListener('resize', this.updateDimensions);
     }
   
     updateDimensions() {
       this.setState({
         width: window.innerWidth,
         height: window.innerHeight,
       });
     }
   
     render() {
       return (
         <span>
           {this.state.width} x {this.state.height}
         </span>
       );
     }
   }
   

⬆ Back to Top

1. What is the difference between setState() and replaceState() methods?¶

   When you use setState() the current and previous states are merged. replaceState() throws out the current state, and replaces it with only what you provide. Usually setState() is used unless you really need to remove all previous keys for some reason. You can also set state to false/null in setState() instead of using replaceState().

⬆ Back to Top

1. How to listen to state changes?¶

   The componentDidUpdate lifecycle method will be called when state changes. You can compare provided state and props values with current state and props to determine if something meaningful changed.

   componentDidUpdate(object prevProps, object prevState)
   

   Note: The previous releases of ReactJS also uses componentWillUpdate(object nextProps, object nextState) for state changes. It has been deprecated in latest releases.

⬆ Back to Top

1. What is the recommended approach of removing an array element in React state?¶

   The better approach is to use Array.prototype.filter() method.

   For example, let's create a removeItem() method for updating the state.

   removeItem(index) {
     this.setState({
       data: this.state.data.filter((item, i) => i !== index)
     })
   }
   

⬆ Back to Top

1. Is it possible to use React without rendering HTML?¶

   It is possible with latest version (>=16.2). Below are the possible options:

   ```jsx harmony render() { return false }

   ```jsx harmony
   render() {
     return null
   }
   

   ```jsx harmony render() { return [] }

   ```jsx harmony
   render() {
     return <React.Fragment></React.Fragment>
   }
   

   jsx harmony render() { return <> }

   Returning undefined won't work.

⬆ Back to Top

1. How to pretty print JSON with React?¶

   We can use <pre> tag so that the formatting of the JSON.stringify() is retained:

   ```jsx harmony const data = { name: 'John', age: 42 };

   class User extends React.Component { render() { return

   {JSON.stringify(data, null, 2)}

   ; } }

   React.render(, document.getElementById('container')); ```

⬆ Back to Top

1. Why you can't update props in React?¶

   The React philosophy is that props should be immutable and top-down. This means that a parent can send any prop values to a child, but the child can't modify received props.

⬆ Back to Top

1. How to focus an input element on page load?¶

   You can do it by creating ref for input element and using it in componentDidMount():

   ```jsx harmony class App extends React.Component { componentDidMount() { this.nameInput.focus(); }

   render() { return (

   (this.nameInput = input)} defaultValue={'Will focus'} />
   ); } }

   ReactDOM.render(, document.getElementById('app')); ```

⬆ Back to Top

1. What are the possible ways of updating objects in state?¶

   1. Calling setState() with an object to merge with state:

      • Using Object.assign() to create a copy of the object:

      const user = Object.assign({}, this.state.user, { age: 42 });
      this.setState({ user });
      

      • Using spread operator:

      const user = { ...this.state.user, age: 42 };
      this.setState({ user });
      

   2. Calling setState() with a function:

      this.setState(prevState => ({
        user: {
          ...prevState.user,
          age: 42,
        },
      }));
      

⬆ Back to Top

1. How can we find the version of React at runtime in the browser?¶

   You can use React.version to get the version.

   ```jsx harmony const REACT_VERSION = React.version;

   ReactDOM.render(

   {React version: ${REACT_VERSION}}
   , document.getElementById('app') ); ```

⬆ Back to Top

1. What are the approaches to include polyfills in your create-react-app?¶

   There are approaches to include polyfills in create-react-app,

   1. Manual import from core-js:

      Create a file called (something like) polyfills.js and import it into root index.js file. Run npm install core-js or yarn add core-js and import your specific required features.

      import 'core-js/fn/array/find';
      import 'core-js/fn/array/includes';
      import 'core-js/fn/number/is-nan';
      

   2. Using Polyfill service:

      Use the polyfill.io CDN to retrieve custom, browser-specific polyfills by adding this line to index.html:

      <script src="https://cdn.polyfill.io/v2/polyfill.min.js?features=default,Array.prototype.includes"></script>
      

      In the above script we had to explicitly request the Array.prototype.includes feature as it is not included in the default feature set.

⬆ Back to Top

1. How to use https instead of http in create-react-app?¶

   You just need to use HTTPS=true configuration. You can edit your package.json scripts section:

   "scripts": {
     "start": "set HTTPS=true && react-scripts start"
   }
   

   or just run set HTTPS=true && npm start

⬆ Back to Top

1. How to avoid using relative path imports in create-react-app?¶

   Create a file called .env in the project root and write the import path:

   NODE_PATH=src/app
   

   After that restart the development server. Now you should be able to import anything inside src/app without relative paths.

⬆ Back to Top

1. How to add Google Analytics for React Router?¶

   Add a listener on the history object to record each page view:

   history.listen(function(location) {
     window.ga('set', 'page', location.pathname + location.search);
     window.ga('send', 'pageview', location.pathname + location.search);
   });
   

⬆ Back to Top

1. How to update a component every second?¶

   You need to use setInterval() to trigger the change, but you also need to clear the timer when the component unmounts to prevent errors and memory leaks.

   componentDidMount() {
     this.interval = setInterval(() => this.setState({ time: Date.now() }), 1000)
   }
   
   componentWillUnmount() {
     clearInterval(this.interval)
   }
   

⬆ Back to Top

1. How do you apply vendor prefixes to inline styles in React?¶

   React does not apply vendor prefixes automatically. You need to add vendor prefixes manually.

   jsx harmony <div style={{ transform: 'rotate(90deg)', WebkitTransform: 'rotate(90deg)', // note the capital 'W' here msTransform: 'rotate(90deg)', // 'ms' is the only lowercase vendor prefix }} />

⬆ Back to Top

1. How to import and export components using React and ES6?¶

   You should use default for exporting the components

   ```jsx harmony import React from 'react'; import User from 'user';

   export default class MyProfile extends React.Component { render() { return //...; } } ```

   With the export specifier, the MyProfile is going to be the member and exported to this module and the same can be imported without mentioning the name in other components.

⬆ Back to Top

1. Why is a component constructor called only once?¶

   React's reconciliation algorithm assumes that without any information to the contrary, if a custom component appears in the same place on subsequent renders, it's the same component as before, so reuses the previous instance rather than creating a new one.

⬆ Back to Top

1. How to define constants in React?¶

   You can use ES7 static field to define constant.

   class MyComponent extends React.Component {
     static DEFAULT_PAGINATION = 10;
   }
   

   Static fields are part of the Class Fields stage 3 proposal.

⬆ Back to Top

1. How to programmatically trigger click event in React?¶

   You could use the ref prop to acquire a reference to the underlying HTMLInputElement object through a callback, store the reference as a class property, then use that reference to later trigger a click from your event handlers using the HTMLElement.click method.

   This can be done in two steps:

   1. Create ref in render method:

      jsx harmony <input ref={input => (this.inputElement = input)} />

   2. Apply click event in your event handler:

      this.inputElement.click();
      

⬆ Back to Top

1. Is it possible to use async/await in plain React?¶

   If you want to use async/await in React, you will need Babel and transform-async-to-generator plugin. React Native ships with Babel and a set of transforms.

⬆ Back to Top

1. What are the common folder structures for React?¶

   There are two common practices for React project file structure.

   1. Grouping by features or routes:

      One common way to structure projects is locate CSS, JS, and tests together, grouped by feature or route.

      common/
      ├─ Avatar.js
      ├─ Avatar.css
      ├─ APIUtils.js
      └─ APIUtils.test.js
      feed/
      ├─ index.js
      ├─ Feed.js
      ├─ Feed.css
      ├─ FeedStory.js
      ├─ FeedStory.test.js
      └─ FeedAPI.js
      profile/
      ├─ index.js
      ├─ Profile.js
      ├─ ProfileHeader.js
      ├─ ProfileHeader.css
      └─ ProfileAPI.js
      

   2. Grouping by file type:

      Another popular way to structure projects is to group similar files together.

      api/
      ├─ APIUtils.js
      ├─ APIUtils.test.js
      ├─ ProfileAPI.js
      └─ UserAPI.js
      components/
      ├─ Avatar.js
      ├─ Avatar.css
      ├─ Feed.js
      ├─ Feed.css
      ├─ FeedStory.js
      ├─ FeedStory.test.js
      ├─ Profile.js
      ├─ ProfileHeader.js
      └─ ProfileHeader.css
      

⬆ Back to Top

1. What are the popular packages for animation?¶

   React Transition Group and React Motion are popular animation packages in React ecosystem.

⬆ Back to Top

1. What is the benefit of styles modules?¶

   It is recommended to avoid hard coding style values in components. Any values that are likely to be used across different UI components should be extracted into their own modules.

   For example, these styles could be extracted into a separate component:

   export const colors = {
     white,
     black,
     blue,
   };
   
   export const space = [0, 8, 16, 32, 64];
   

   And then imported individually in other components:

   import { space, colors } from './styles';
   

⬆ Back to Top

1. What are the popular React-specific linters?¶

   ESLint is a popular JavaScript linter. There are plugins available that analyse specific code styles. One of the most common for React is an npm package called eslint-plugin-react. By default, it will check a number of best practices, with rules checking things from keys in iterators to a complete set of prop types.

   Another popular plugin is eslint-plugin-jsx-a11y, which will help fix common issues with accessibility. As JSX offers slightly different syntax to regular HTML, issues with alt text and tabindex, for example, will not be picked up by regular plugins.

⬆ Back to Top

1. How to make AJAX call and in which component lifecycle methods should I make an AJAX call?¶

   You can use AJAX libraries such as Axios, jQuery AJAX, and the browser built-in fetch. You should fetch data in the componentDidMount() lifecycle method. This is so you can use setState() to update your component when the data is retrieved.

   For example, the employees list fetched from API and set local state:

   ```jsx harmony class MyComponent extends React.Component { constructor(props) { super(props); this.state = { employees: [], error: null, }; }

   componentDidMount() { fetch('https://api.example.com/items') .then(res => res.json()) .then( result => { this.setState({ employees: result.employees, }); }, error => { this.setState({ error }); } ); }

   render() { const { error, employees } = this.state; if (error) { return

   Error: {error.message}
   ; } else { return (
   {employees.map(employee => (
   • {employee.name}-{employee.experience}
   ))}
   ); } } } ```

⬆ Back to Top

1. What are render props?¶

   Render Props is a simple technique for sharing code between components using a prop whose value is a function. The below component uses render prop which returns a React element.

   jsx harmony <DataProvider render={data => <h1>{`Hello ${data.target}`}</h1>} />

   Libraries such as React Router and DownShift are using this pattern.

React Router¶

⬆ Back to Top

1. What is React Router?¶

   React Router is a powerful routing library built on top of React that helps you add new screens and flows to your application incredibly quickly, all while keeping the URL in sync with what's being displayed on the page.

⬆ Back to Top

1. How React Router is different from history library?¶

   React Router is a wrapper around the history library which handles interaction with the browser's window.history with its browser and hash histories. It also provides memory history which is useful for environments that don't have global history, such as mobile app development (React Native) and unit testing with Node.

⬆ Back to Top

1. What are the <Router> components of React Router v4?¶

   React Router v4 provides below 3 <Router> components:

   1. <BrowserRouter>
   2. <HashRouter>
   3. <MemoryRouter>

   The above components will create browser, hash, and memory history instances. React Router v4 makes the properties and methods of the history instance associated with your router available through the context in the router object.

⬆ Back to Top

1. What is the purpose of push() and replace() methods of history?¶

   A history instance has two methods for navigation purpose.

   1. push()
   2. replace()

   If you think of the history as an array of visited locations, push() will add a new location to the array and replace() will replace the current location in the array with the new one.

⬆ Back to Top

1. How do you programmatically navigate using React Router v4?¶

   There are three different ways to achieve programmatic routing/navigation within components.

   1. Using the withRouter() higher-order function:

      The withRouter() higher-order function will inject the history object as a prop of the component. This object provides push() and replace() methods to avoid the usage of context.

      ```jsx harmony import { withRouter } from 'react-router-dom'; // this also works with 'react-router-native'

      const Button = withRouter(({ history }) => ( { history.push('/new-location'); }}

      {'Click Me!'}
      

      )); ```

   2. Using <Route> component and render props pattern:

      The <Route> component passes the same props as withRouter(), so you will be able to access the history methods through the history prop.

      ```jsx harmony import { Route } from 'react-router-dom';

      const Button = () => ( ( { history.push('/new-location'); }} > {'Click Me!'} )} /> ); ```

   3. Using context:

      This option is not recommended and treated as unstable API.

      ```jsx harmony const Button = (props, context) => ( { context.history.push('/new-location'); }}

      {'Click Me!'}
      

      );

      Button.contextTypes = { history: React.PropTypes.shape({ push: React.PropTypes.func.isRequired, }), }; ```

⬆ Back to Top

1. How to get query parameters in React Router v4?¶

   The ability to parse query strings was taken out of React Router v4 because there have been user requests over the years to support different implementation. So the decision has been given to users to choose the implementation they like. The recommended approach is to use query strings library.

   const queryString = require('query-string');
   const parsed = queryString.parse(props.location.search);
   

   You can also use URLSearchParams if you want something native:

   const params = new URLSearchParams(props.location.search);
   const foo = params.get('name');
   

   You should use a polyfill for IE11.

⬆ Back to Top

1. Why you get "Router may have only one child element" warning?¶

   You have to wrap your Route's in a <Switch> block because <Switch> is unique in that it renders a route exclusively.

   At first you need to add Switch to your imports:

   import { Switch, Router, Route } from 'react-router';
   

   Then define the routes within <Switch> block:

   jsx harmony <Router> <Switch> <Route {/* ... */} /> <Route {/* ... */} /> </Switch> </Router>

⬆ Back to Top

1. How to pass params to history.push method in React Router v4?¶

   While navigating you can pass props to the history object:

   this.props.history.push({
     pathname: '/template',
     search: '?name=sudheer',
     state: { detail: response.data },
   });
   

   The search property is used to pass query params in push() method.

⬆ Back to Top

1. How to implement default or NotFound page?¶

   A <Switch> renders the first child <Route> that matches. A <Route> with no path always matches. So you just need to simply drop path attribute as below

   jsx harmony <Switch> <Route exact path="/" component={Home} /> <Route path="/user" component={User} /> <Route component={NotFound} /> </Switch>

⬆ Back to Top

1. How to get history on React Router v4?¶

   Below are the list of steps to get history object on React Router v4,

   1. Create a module that exports a history object and import this module across the project.

      For example, create history.js file:

      import { createBrowserHistory } from 'history';
      
      export default createBrowserHistory({
        /* pass a configuration object here if needed */
      });
      

   2. You should use the <Router> component instead of built-in routers. Imported the above history.js inside index.js file:

      ```jsx harmony import { Router } from 'react-router-dom'; import history from './history'; import App from './App';

      ReactDOM.render( , holder ); ```

   3. You can also use push method of history object similar to built-in history object:

      // some-other-file.js
      import history from './history';
      
      history.push('/go-here');
      

⬆ Back to Top

1. How to perform automatic redirect after login?¶

   The react-router package provides <Redirect> component in React Router. Rendering a <Redirect> will navigate to a new location. Like server-side redirects, the new location will override the current location in the history stack.

   import React, { Component } from 'react';
   import { Redirect } from 'react-router';
   
   export default class LoginComponent extends Component {
     render() {
       if (this.state.isLoggedIn === true) {
         return <Redirect to="/your/redirect/page" />;
       } else {
         return <div>{'Login Please'}</div>;
       }
     }
   }
   

React Internationalization¶

⬆ Back to Top

1. What is React Intl?¶

   The React Intl library makes internalization in React straightforward, with off-the-shelf components and an API that can handle everything from formatting strings, dates, and numbers, to pluralization. React Intl is part of FormatJS which provides bindings to React via its components and API.

⬆ Back to Top

1. What are the main features of React Intl?¶

   Below are the main features of React Intl,

   1. Display numbers with separators.
   2. Display dates and times correctly.
   3. Display dates relative to "now".
   4. Pluralize labels in strings.
   5. Support for 150+ languages.
   6. Runs in the browser and Node.
   7. Built on standards.

⬆ Back to Top

1. What are the two ways of formatting in React Intl?¶

   The library provides two ways to format strings, numbers, and dates:

   1. Using react components:

      jsx harmony <FormattedMessage id={'account'} defaultMessage={'The amount is less than minimum balance.'} />

   2. Using an API:

      const messages = defineMessages({
        accountMessage: {
          id: 'account',
          defaultMessage: 'The amount is less than minimum balance.',
        }
      })
      
      formatMessage(messages.accountMessage)
      

⬆ Back to Top

1. How to use <FormattedMessage> as placeholder using React Intl?¶

   The <Formatted... /> components from react-intl return elements, not plain text, so they can't be used for placeholders, alt text, etc. In that case, you should use lower level API formatMessage(). You can inject the intl object into your component using injectIntl() higher-order component and then format the message using formatMessage() available on that object.

   ```jsx harmony import React from 'react'; import { injectIntl, intlShape } from 'react-intl';

   const MyComponent = ({ intl }) => { const placeholder = intl.formatMessage({ id: 'messageId' }); return ; };

   MyComponent.propTypes = { intl: intlShape.isRequired, };

   export default injectIntl(MyComponent); ```

⬆ Back to Top

1. How to access current locale with React Intl?¶

   You can get the current locale in any component of your application using injectIntl():

   ```jsx harmony import { injectIntl, intlShape } from 'react-intl';

   const MyComponent = ({ intl }) => (

   {The current locale is ${intl.locale}}
   );

   MyComponent.propTypes = { intl: intlShape.isRequired, };

   export default injectIntl(MyComponent); ```

⬆ Back to Top

1. How to format date using React Intl?¶

   The injectIntl() higher-order component will give you access to the formatDate() method via the props in your component. The method is used internally by instances of FormattedDate and it returns the string representation of the formatted date.

   ```jsx harmony import { injectIntl, intlShape } from 'react-intl';

   const stringDate = this.props.intl.formatDate(date, { year: 'numeric', month: 'numeric', day: 'numeric', });

   const MyComponent = ({ intl }) => (

   {The formatted date is ${stringDate}}
   );

   MyComponent.propTypes = { intl: intlShape.isRequired, };

   export default injectIntl(MyComponent); ```

React Testing¶

⬆ Back to Top

1. What is Shallow Renderer in React testing?¶

   Shallow rendering is useful for writing unit test cases in React. It lets you render a component one level deep and assert facts about what its render method returns, without worrying about the behavior of child components, which are not instantiated or rendered.

   For example, if you have the following component:

   function MyComponent() {
     return (
       <div>
         <span className={'heading'}>{'Title'}</span>
         <span className={'description'}>{'Description'}</span>
       </div>
     );
   }
   

   Then you can assert as follows:

   ```jsx harmony import ShallowRenderer from 'react-test-renderer/shallow';

   // in your test const renderer = new ShallowRenderer(); renderer.render();

   const result = renderer.getRenderOutput();

   expect(result.type).toBe('div'); expect(result.props.children).toEqual([ {'Title'}, {'Description'}, ]); ```

⬆ Back to Top

1. What is TestRenderer package in React?¶

   This package provides a renderer that can be used to render components to pure JavaScript objects, without depending on the DOM or a native mobile environment. This package makes it easy to grab a snapshot of the platform view hierarchy (similar to a DOM tree) rendered by a ReactDOM or React Native without using a browser or jsdom.

   ```jsx harmony import TestRenderer from 'react-test-renderer';

   const Link = ({ page, children }) => {children};

   const testRenderer = TestRenderer.create( {'Facebook'} );

   console.log(testRenderer.toJSON()); // { // type: 'a', // props: { href: 'https://www.facebook.com/' }, // children: [ 'Facebook' ] // } ```

⬆ Back to Top

1. What is the purpose of ReactTestUtils package?¶

   ReactTestUtils are provided in the with-addons package and allow you to perform actions against a simulated DOM for the purpose of unit testing.

⬆ Back to Top

1. What is Jest?¶

   Jest is a JavaScript unit testing framework created by Facebook based on Jasmine and provides automated mock creation and a jsdom environment. It's often used for testing components.

⬆ Back to Top

1. What are the advantages of Jest over Jasmine?¶

   There are couple of advantages compared to Jasmine:

   • Automatically finds tests to execute in your source code.
   • Automatically mocks dependencies when running your tests.
   • Allows you to test asynchronous code synchronously.
   • Runs your tests with a fake DOM implementation (via jsdom) so that your tests can be run on the command line.
   • Runs tests in parallel processes so that they finish sooner.

⬆ Back to Top

1. Give a simple example of Jest test case¶

   Let's write a test for a function that adds two numbers in sum.js file:

   const sum = (a, b) => a + b;
   
   export default sum;
   

   Create a file named sum.test.js which contains actual test:

   import sum from './sum';
   
   test('adds 1 + 2 to equal 3', () => {
     expect(sum(1, 2)).toBe(3);
   });
   

   And then add the following section to your package.json:

   {
     "scripts": {
       "test": "jest"
     }
   }
   

   Finally, run yarn test or npm test and Jest will print a result:

   $ yarn test
   PASS ./sum.test.js
   ✓ adds 1 + 2 to equal 3 (2ms)
   

React Redux¶

⬆ Back to Top

1. What is flux?¶

   Flux is an application design paradigm used as a replacement for the more traditional MVC pattern. It is not a framework or a library but a new kind of architecture that complements React and the concept of Unidirectional Data Flow. Facebook uses this pattern internally when working with React.

   The workflow between dispatcher, stores and views components with distinct inputs and outputs as follows:

   

⬆ Back to Top

1. What is Redux?¶

   Redux is a predictable state container for JavaScript apps based on the Flux design pattern. Redux can be used together with React, or with any other view library. It is tiny (about 2kB) and has no dependencies.

⬆ Back to Top

1. What are the core principles of Redux?¶

   Redux follows three fundamental principles:

   1. Single source of truth: The state of your whole application is stored in an object tree within a single store. The single state tree makes it easier to keep track of changes over time and debug or inspect the application.
   2. State is read-only: The only way to change the state is to emit an action, an object describing what happened. This ensures that neither the views nor the network callbacks will ever write directly to the state.
   3. Changes are made with pure functions: To specify how the state tree is transformed by actions, you write reducers. Reducers are just pure functions that take the previous state and an action as parameters, and return the next state.

⬆ Back to Top

1. What are the downsides of Redux compared to Flux?¶

   Instead of saying downsides we can say that there are few compromises of using Redux over Flux. Those are as follows:

   1. You will need to learn to avoid mutations: Flux is un-opinionated about mutating data, but Redux doesn't like mutations and many packages complementary to Redux assume you never mutate the state. You can enforce this with dev-only packages like redux-immutable-state-invariant, Immutable.js, or instructing your team to write non-mutating code.
   2. You're going to have to carefully pick your packages: While Flux explicitly doesn't try to solve problems such as undo/redo, persistence, or forms, Redux has extension points such as middleware and store enhancers, and it has spawned a rich ecosystem.
   3. There is no nice Flow integration yet: Flux currently lets you do very impressive static type checks which Redux doesn't support yet.

⬆ Back to Top

1. What is the difference between mapStateToProps() and mapDispatchToProps()?¶

   mapStateToProps() is a utility which helps your component get updated state (which is updated by some other components):

   const mapStateToProps = state => {
     return {
       todos: getVisibleTodos(state.todos, state.visibilityFilter),
     };
   };
   

   mapDispatchToProps() is a utility which will help your component to fire an action event (dispatching action which may cause change of application state):

   const mapDispatchToProps = dispatch => {
     return {
       onTodoClick: id => {
         dispatch(toggleTodo(id));
       },
     };
   };
   

   Recommend always using the “object shorthand” form for the mapDispatchToProps

   Redux wrap it in another function that looks like (…args) => dispatch(onTodoClick(…args)), and pass that wrapper function as a prop to your component.

   const mapDispatchToProps = {
     onTodoClick,
   };
   

⬆ Back to Top

1. Can I dispatch an action in reducer?¶

   Dispatching an action within a reducer is an anti-pattern. Your reducer should be without side effects, simply digesting the action payload and returning a new state object. Adding listeners and dispatching actions within the reducer can lead to chained actions and other side effects.

⬆ Back to Top

1. How to access Redux store outside a component?¶

   You just need to export the store from the module where it created with createStore(). Also, it shouldn't pollute the global window object.

   store = createStore(myReducer);
   
   export default store;
   

⬆ Back to Top

1. What are the drawbacks of MVW pattern?¶

   1. DOM manipulation is very expensive which causes applications to behave slow and inefficient.
   2. Due to circular dependencies, a complicated model was created around models and views.
   3. Lot of data changes happens for collaborative applications(like Google Docs).
   4. No way to do undo (travel back in time) easily without adding so much extra code.

⬆ Back to Top

1. Are there any similarities between Redux and RxJS?¶

   These libraries are very different for very different purposes, but there are some vague similarities.

   Redux is a tool for managing state throughout the application. It is usually used as an architecture for UIs. Think of it as an alternative to (half of) Angular. RxJS is a reactive programming library. It is usually used as a tool to accomplish asynchronous tasks in JavaScript. Think of it as an alternative to Promises. Redux uses the Reactive paradigm because the Store is reactive. The Store observes actions from a distance, and changes itself. RxJS also uses the Reactive paradigm, but instead of being an architecture, it gives you basic building blocks, Observables, to accomplish this pattern.

⬆ Back to Top

1. How to dispatch an action on load?¶

   You can dispatch an action in componentDidMount() method and in render() method you can verify the data.

   class App extends Component {
     componentDidMount() {
       this.props.fetchData();
     }
   
     render() {
       return this.props.isLoaded ? (
         <div>{'Loaded'}</div>
       ) : (
         <div>{'Not Loaded'}</div>
       );
     }
   }
   
   const mapStateToProps = state => ({
     isLoaded: state.isLoaded,
   });
   
   const mapDispatchToProps = { fetchData };
   
   export default connect(mapStateToProps, mapDispatchToProps)(App);
   

⬆ Back to Top

1. How to use connect() from React Redux?¶

   You need to follow two steps to use your store in your container:

   1. Use mapStateToProps(): It maps the state variables from your store to the props that you specify.

   2. Connect the above props to your container: The object returned by the mapStateToProps function is connected to the container. You can import connect() from react-redux.

      ```jsx harmony import React from 'react'; import { connect } from 'react-redux';

      class App extends React.Component { render() { return

      {this.props.containerData}
      ; } }

      function mapStateToProps(state) { return { containerData: state.data }; }

      export default connect(mapStateToProps)(App); ```

⬆ Back to Top

1. How to reset state in Redux?¶

   You need to write a root reducer in your application which delegate handling the action to the reducer generated by combineReducers().

   For example, let us take rootReducer() to return the initial state after USER_LOGOUT action. As we know, reducers are supposed to return the initial state when they are called with undefined as the first argument, no matter the action.

   const appReducer = combineReducers({
     /* your app's top-level reducers */
   });
   
   const rootReducer = (state, action) => {
     if (action.type === 'USER_LOGOUT') {
       state = undefined;
     }
   
     return appReducer(state, action);
   };
   

   In case of using redux-persist, you may also need to clean your storage. redux-persist keeps a copy of your state in a storage engine. First, you need to import the appropriate storage engine and then, to parse the state before setting it to undefined and clean each storage state key.

   const appReducer = combineReducers({
     /* your app's top-level reducers */
   });
   
   const rootReducer = (state, action) => {
     if (action.type === 'USER_LOGOUT') {
       Object.keys(state).forEach(key => {
         storage.removeItem(`persist:${key}`);
       });
   
       state = undefined;
     }
   
     return appReducer(state, action);
   };
   

⬆ Back to Top

1. Whats the purpose of at symbol in the Redux connect decorator?¶

   The @ symbol is in fact a JavaScript expression used to signify decorators. Decorators make it possible to annotate and modify classes and properties at design time.

   Let's take an example setting up Redux without and with a decorator.

   • Without decorator:

   import React from 'react';
   import * as actionCreators from './actionCreators';
   import { bindActionCreators } from 'redux';
   import { connect } from 'react-redux';
   
   function mapStateToProps(state) {
     return { todos: state.todos };
   }
   
   function mapDispatchToProps(dispatch) {
     return { actions: bindActionCreators(actionCreators, dispatch) };
   }
   
   class MyApp extends React.Component {
     // ...define your main app here
   }
   
   export default connect(mapStateToProps, mapDispatchToProps)(MyApp);
   

   • With decorator:

   import React from 'react';
   import * as actionCreators from './actionCreators';
   import { bindActionCreators } from 'redux';
   import { connect } from 'react-redux';
   
   function mapStateToProps(state) {
     return { todos: state.todos };
   }
   
   function mapDispatchToProps(dispatch) {
     return { actions: bindActionCreators(actionCreators, dispatch) };
   }
   
   @connect(mapStateToProps, mapDispatchToProps)
   export default class MyApp extends React.Component {
     // ...define your main app here
   }
   

   The above examples are almost similar except the usage of decorator. The decorator syntax isn't built into any JavaScript runtimes yet, and is still experimental and subject to change. You can use babel for the decorators support.

⬆ Back to Top

1. What is the difference between React context and React Redux?¶

   You can use Context in your application directly and is going to be great for passing down data to deeply nested components which what it was designed for.

   Whereas Redux is much more powerful and provides a large number of features that the Context API doesn't provide. Also, React Redux uses context internally but it doesn't expose this fact in the public API.

⬆ Back to Top

1. Why are Redux state functions called reducers?¶

   Reducers always return the accumulation of the state (based on all previous and current actions). Therefore, they act as a reducer of state. Each time a Redux reducer is called, the state and action are passed as parameters. This state is then reduced (or accumulated) based on the action, and then the next state is returned. You could reduce a collection of actions and an initial state (of the store) on which to perform these actions to get the resulting final state.

⬆ Back to Top

1. How to make AJAX request in Redux?¶

   You can use redux-thunk middleware which allows you to define async actions.

   Let's take an example of fetching specific account as an AJAX call using fetch API:

   export function fetchAccount(id) {
     return dispatch => {
       dispatch(setLoadingAccountState()); // Show a loading spinner
       fetch(`/account/${id}`, response => {
         dispatch(doneFetchingAccount()); // Hide loading spinner
         if (response.status === 200) {
           dispatch(setAccount(response.json)); // Use a normal function to set the received state
         } else {
           dispatch(someError);
         }
       });
     };
   }
   
   function setAccount(data) {
     return { type: 'SET_Account', data: data };
   }