368

I have a React component, and inside the render method of the component I have something like this:

render() {
    return (
        <div>
            <div>
                // removed for brevity
            </div>

           { switch(...) {} }

            <div>
                // removed for brevity
            </div>
        </div>
    );
}

Now the point is that I have two div elements, one at the top and one at the bottom, that are fixed. In the middle I want to have a switch statement, and according to a value in my state I want to render a different component. So basically, I want the two div elements to be fixed always, and just in the middle to render a different component each time. I'm using this to implement a multi-step payment procedure). Though, as is the code currently it doesn't work, as it gives me an error saying that switch is unexpected. Any ideas how to achieve what I want?

3
  • 1
    Well, you don't need to have all that logic in the return statement or even the render method for that matter. Could you define each <div> as a const, and then use the switch before your return to determine which <div> should be rendered? Commented Oct 5, 2017 at 18:58
  • @JaredGoguen But then, I would need to repeat the div at the top and bottom, multiple times for each case of the switch. Or I just misunderstood, you.. Commented Oct 5, 2017 at 18:59
  • no, you could create code for let middleDiv = ... and then include {middleDiv} in your return JSX between the two <div>s that you have hard-coded there. Commented Oct 5, 2017 at 19:00

30 Answers 30

504

Try this, which is way cleaner too: Get that switch out of the render in a function and just call it passing the params you want. For example:

renderSwitch(param) {
  switch(param) {
    case 'foo':
      return 'bar';
    default:
      return 'foo';
  }
}

render() {
  return (
    <div>
      <div>
          // removed for brevity
      </div>
      {this.renderSwitch(param)}
      <div>
          // removed for brevity
      </div>
    </div>
  );
}
Sign up to request clarification or add additional context in comments.

2 Comments

If you put the function call in the return it always calls on rendering. So, if you need to call renderSwitch from somewhere else other than the return statement this won't work.
Furthermore, it gets called multiple times.
338

In contrast to other answers, I would prefer to inline the "switch" in the render function. It makes it more clear what components can be rendered at that position. You can implement a switch-like expression by using a plain old javascript object:

render () {
  return (
    <div>
      <div>
        {/* removed for brevity */}
      </div>
      {
        {
          'foo': <Foo />,
          'bar': <Bar />
        }[param]
      }
      <div>
        {/* removed for brevity */}
      </div>
    </div>
  )
}

19 Comments

This approach has its limits and overhead. Each of your views will be processed and will depend on the current state/props which might not exist. Ex: lets say you wanted to either render: <SearchResults /> or <NoResults />. If the view state should render <NoResults />, <SearchResults /> might not compile because it depends on properties that don't yet exist.
What about a default case?
@lama12345 For default case, use || as follows: { 'foo': <Foo />, 'bar': <Bar /> }[param] || <Baz />
This looks awesome! Any idea how to use enums as the keys for this object? I.e.: MyEnum.Foo: <Foo />, MyEnum.Bar: <Bar /> My compiler complains about an unexpected token with the dot in between MyEnum and Foo
@OfekGila same as defining any weird object keys, so like [MyEnum.Foo]: <Foo />
|
122

That's happening, because switch statement is a statement, but here javascript expects an expression.

Although, it's not recommended to use switch statement in a render method, you can use self-invoking function to achieve this:

render() {
    // Don't forget to return a value in a switch statement
    return (
        <div>
            {(() => {
                switch(...) {}
            })()}
        </div>
    );
}

4 Comments

Thanks I used that like: render () { return ( <div> {(() => { switch (this.state.type) { case commons.HARD_SOFT: return <HardSoft params={this.state.param} onSubmitHead={this.onSubmit} />; } })()} </div> );
Why is it not recommended?
Likely he read something somewhere that says not to do it because it's ugly to someone somehow. A lot of people don't like switch statements for varying reasons. While it's not mentioned in the React documentation, conditional rendering is obviously supported by React, and switch statements don't cause any issues with React.
How would this work? I get a reference error tab is not defined for my switch statement.
61

I did this inside the render() method:

  render() {
    const project = () => {
      switch(this.projectName) {

        case "one":   return <ComponentA />;
        case "two":   return <ComponentB />;
        case "three": return <ComponentC />;
        case "four":  return <ComponentD />;

        default:      return <h1>No project match</h1>
      }
    }

    return (
      <div>{ project() }</div>
    )
  }

I tried to keep the render() return clean, so I put my logic in a 'const' function right above. This way I can also indent my switch cases neatly.

2 Comments

@a_m_dev Instead of a 'const project' function inside the render method, we can place it as a component method, then call it inside render return like "<div>{ this.project() }</div>". Unless you're talking about not using switch at all, then I can think of using if / else, or show / hide components using className by updating the state.
that could be good even more , because for example i use a head() method of my route components to inject the data by react-helmet to the head of my document
53

I'm not a big fan of any of the current answers, because they are either too verbose, or require you to jump around the code to understand what is going on.

I prefer doing this in a more react component centred way, by creating a <Switch/>. The job of this component is to take a prop, and only render children whose child prop matches this one. So in the example below I have created a test prop on the switch, and compared it to a value prop on the children, only rendering the ones that match.

Example:

const Switch = props => {
  const { test, children } = props
  // filter out only children with a matching prop
  return children.find(child => {
    return child.props.value === test
  })      
}

const Sample = props => {
  const someTest = true
  return (
    <Switch test={someTest}>
      <div value={false}>Will display if someTest is false</div>
      <div value={true}>Will display if someTest is true</div>
    </Switch>
  )
}

ReactDOM.render(
  <Sample/>,
  document.getElementById("react")
);
<script src="https://cdnjs.cloudflare.com/ajax/libs/react/16.6.3/umd/react.production.min.js"></script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/react-dom/16.6.3/umd/react-dom.production.min.js"></script>
<div id="react"></div>

You can make the switch as simple or as complex as you want. Don't forget to perform more robust checking of the children and their value props.

4 Comments

Exactly what I was looking for! Here is a little improvement: javascript const Switch = props => { const { test, children } = props; return children.find(child => { return child.props.value === test; }); }; const Case = ({ children, value }) => { return children; // I don't want do add container around my cases ! }; That way you can write: javascript <Switch test={true}> <Case value={true}> <ItAlwaysFeelsRightToBeTrue /> </Case> <Case value={false}> <FalseAlarm /> </Case> </Switch>
@MattWay While this a good option for pure JS, it throws a TS error when target is set to es5 as property find does not exist on ReactNode
@ZakriyaBilal The code is more of a proof of concept, and about how componentising ideas like switches will make your code more react like. The key is just finding a way to compare the props of children.
TypeScript version of this at stackoverflow.com/a/63852247/733092.
40

A way to represent a kind of switch in a render block, using conditional operators:

{(someVar === 1 &&
    <SomeContent/>)
|| (someVar === 2 &&
    <SomeOtherContent />)
|| (this.props.someProp === "something" &&
    <YetSomeOtherContent />)
|| (this.props.someProp === "foo" && this.props.someOtherProp === "bar" &&
    <OtherContentAgain />)
||
    <SomeDefaultContent />
}

It should be ensured that the conditions strictly return a boolean.

5 Comments

Nice and elegant and can be used right in the render block. Best answer IMHO
I noticed this is a violation of EsLints rules eslint.org/docs/rules/no-mixed-operators mixing && and ||
@FishFingers I noticed that too when I tried to use it exactly as above. It can be easily avoided by wrapping each "case" in parentheses.
Are there any benefits of this over a plain switch? Switch is cleaner and easy to see what goes where, this is pretty convoluted to do the same thing IMO. Where is the next && and then ||, what happens if OR this AND that..
@James that's a method whose state of mind, and consequently benefits, are the same as for "Inline If with conditional operator" mentioned by the React documentation: reactjs.org/docs/…. I'd even say it's simply an extension of it. Preferring to separate some rendering logic from the render block is a subjective choice, and proficiency with conditional operators is something personal.
37

Although this is yet another way to do it, if you have gone all-in on hooks, you could take advantage of useCallback to produce a function that is only recreated when necessary.

Let's say you have a component which should be rendered according to a status prop. With hooks, you could implement this as follows:

const MyComponent = ({ status }) => {
  const renderContent = React.useCallback(() => {
    switch(status) {
      case 'CONNECTING': 
        return <p className="connecting">Connecting...</p>;
      
      case 'CONNECTED': 
        return <p className="success">Connected Successfully!</p>

      default: 
        return null;
      
    }
  }, [status]);

  return (
    <div className="container">
      {renderContent()}
    </div>
  );
};

I like this because:

  • It's obvious what is going on - a function is created, and then later called (the immediately invoked anonymous function method looks a little odd, and can potentially confuse newer developers)
  • The useCallback hook ensures that the renderContent callback is reused between renders, unless the depedency status changes
  • The renderContent function uses a closure to access the necessary props passed in to the component. A separate function (like the accepted answer) requires the passing of the props into it, which can be burdensome (especially when using TypeScript, as the parameters should also be typed correctly)

Comments

26

lenkan's answer is a great solution.

<div>
  {{ beep: <div>Beep</div>,
     boop: <div>Boop</div>
  }[greeting]}
</div>

If you need a default value, then you can even do

<div>
  {{ beep: <div>Beep</div>,
     boop: <div>Boop</div>
  }[greeting] || <div>Hello world</div>}
</div>

Alternatively, if that doesn't read well to you, then you can do something like

<div>
  { 
    rswitch(greeting, {
      beep: <div>Beep</div>,
      boop: <div>Boop</div>,
      default: <div>Hello world</div>
    }) 
  }
</div>

with

function rswitch (param, cases) {
  if (cases[param]) {
    return cases[param]
  } else {
    return cases.default
  }
}

2 Comments

{{key1: <Component1 />, ...}[key] is not a good solution. You see, before the selection happens, the whole initial object is constructed - i.e. every branch of the switch is rendered - Component1, Component2, etc...
Yeah, lenkan's answer should be the correct answer, because switch shouldn't be used in functional component. Thanks for adding OR for default case. And dont bother with rswitch(), the map solution is spot on! thumbs up
24

function Notification({ text, status }) {
  return (
    <div>
      {(() => {
        switch (status) {
          case 'info':
            return <Info text={text} />;
          case 'warning':
            return <Warning text={text} />;
          case 'error':
            return <Error text={text} />;
          default:
            return null;
        }
      })()}
    </div>
  );
}

Comments

14
  const [route, setRoute] = useState(INITIAL_ROUTE)

  return (
    <RouteContext.Provider value={{ route, setRoute }}>
      {(() => {
        switch (route) {
          case Route.Home:
            return <PopupHomePage />
          case Route.App:
            return <PopupAppPage />
          default:
            return null
        }
      })()}
    </RouteContext.Provider>

Comments

13

You can do something like this.

 <div>
          { object.map((item, index) => this.getComponent(item, index)) }
 </div>

getComponent(item, index) {
    switch (item.type) {
      case '1':
        return <Comp1/>
      case '2':
        return <Comp2/>
      case '3':
        return <Comp3 />
    }
  }

Comments

8

You can't have a switch in render. The psuedo-switch approach of placing an object-literal that accesses one element isn't ideal because it causes all views to process and that can result in dependency errors of props that don't exist in that state.

Here's a nice clean way to do it that doesn't require each view to render in advance:

render () {
  const viewState = this.getViewState();

  return (
    <div>
      {viewState === ViewState.NO_RESULTS && this.renderNoResults()}
      {viewState === ViewState.LIST_RESULTS && this.renderResults()}
      {viewState === ViewState.SUCCESS_DONE && this.renderCompleted()}
    </div>
  )

If your conditions for which view state are based on more than a simple property – like multiple conditions per line, then an enum and a getViewState function to encapsulate the conditions is a nice way to separate this conditional logic and cleanup your render.

1 Comment

Simple and clean way.
8

A elegant way is to use an array index as dependency:

<Box>
    {
      {
        0: <ComponentOne/>,
        1: <ComponentTwo/>,
        2: <ComponentThree/>,
      }[arrayIndex]         // arrayIndex as dependency
    }
</Box>

Comments

7

I really liked the suggestion in https://stackoverflow.com/a/60313570/770134, so I adapted it to Typescript like so

import React, { FunctionComponent } from 'react'
import { Optional } from "typescript-optional";
const { ofNullable } = Optional

interface SwitchProps {
  test: string
  defaultComponent: JSX.Element
}

export const Switch: FunctionComponent<SwitchProps> = (props) => {
  return ofNullable(props.children)
    .map((children) => {
      return ofNullable((children as JSX.Element[]).find((child) => child.props['value'] === props.test))
        .orElse(props.defaultComponent)
    })
    .orElseThrow(() => new Error('Children are required for a switch component'))
}

const Foo = ({ value = "foo" }) => <div>foo</div>;
const Bar = ({ value = "bar" }) => <div>bar</div>;
const value = "foo";
const SwitchExample = <Switch test={value} defaultComponent={<div />}>
  <Foo />
  <Bar />
</Switch>;

1 Comment

Great. Now add <Case /> like in stackoverflow.com/questions/46592833/… and publish it as a npm package :-)
7

Improved a bit from Matt Way's answer.

export const Switch = ({ test, children }) => {
  const defaultResult = children.find((child) => child.props.default) || null;
  const result = children.find((child) => child.props.value === test);

  return result || defaultResult;
};
export const Case = ({ children }) => children;


const color = getColorFromTheMostComplexFnEver();

<Switch test={color}>
  <Case value="Green">Forest</Case>
  <Case value="Red">Blood</Case>
  <Case default>Predator</Case>
</Switch>
<script src="https://cdnjs.cloudflare.com/ajax/libs/react/16.6.3/umd/react.production.min.js"></script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/react-dom/16.6.3/umd/react-dom.production.min.js"></script>

Comments

7

Alternative: use operators. They dont suffer the same JSX limitations that statements such as 'switch' do.

const Page = () => {
    const [currentView, setCurrentView] = useState('home');

    return <>
        <AppBar />
        {
            currentView === 'home'
            && <HomePage />

            || currentView === 'login'
            && <LoginPage />

            || currentView === 'register'
            && <RegisterPage />

            || <DefaultPage />
        }
    </>;
};

Comments

6
import React from 'react';

import ListView from './ListView';
import TableView from './TableView';

function DataView({
    currView,
    data,
    onSelect,
    onChangeStatus,
    viewTodo,
    editTodo,
    deleteTodo,
}) {
    return (
        <div>
            {(function () {
                switch (currView) {
                    case 'table':
                        return (
                            <TableView
                                todos={data}
                                onSelect={onSelect}
                                onChangeStatus={onChangeStatus}
                                viewTodo={viewTodo}
                                editTodo={editTodo}
                                deleteTodo={deleteTodo}
                            />
                        );

                    case 'list':
                        return (
                            <ListView
                                todos={data}
                                onSelect={onSelect}
                                onChangeStatus={onChangeStatus}
                                viewTodo={viewTodo}
                                editTodo={editTodo}
                                deleteTodo={deleteTodo}
                            />
                        );

                    default:
                        break;
                }
            })()}
        </div>
    );
}

export default DataView;

1 Comment

Like this approach, really handy. Without declare function first. Nice.
4

make it easy and just use many if statements.

for example:

<Grid>
   {yourVar==="val1"&&(<> your code for val1 </>)}
   {yourVar==="val2"&&(<> your code for val2 </>)}
   .... other statments
</Grid>

1 Comment

But then there's no default case, that would cover anything not corresponding to the conditions.
3

How about:

mySwitchFunction = (param) => {
   switch (param) {
      case 'A':
         return ([
            <div />,
         ]);
      // etc...
   }
}
render() {
    return (
       <div>
          <div>
               // removed for brevity
          </div>

          { this.mySwitchFunction(param) }

          <div>
              // removed for brevity
          </div>
      </div>
   );
}

Comments

3

I converted accepted answer to arrow functional component solution and saw James provides similar answer and one can get error not defined. So here is the solution:

  const renderSwitch = (param) => {
    switch (param) {
      case "foo":
        return "bar";
      default:
        return "foo";
    }
  };

  return (
    <div>
      <div></div>

      {renderSwitch(param)}

      <div></div>
    </div>
  );

Comments

3

Switch-Case statement within React Component could be used as follows:

<div  id="time-list">
{   
    (() => {
        switch (groupByFilterId) {
            case 0:/*Case 0 */
                return (
                    <div>Case 0</div>
                )
               break;
           case 1: /*Case 1 */
           return ( 
            <div>Case 1</div>
            )
            break;
           case 2:/*Case 2 */
           return ( 
            <div>Case 2</div>
            )
            break;
        }
     })()}

      
       
    
    </div>

1 Comment

duplicate off my answer
3

We can do this directly using useCallback

const renderContent = useCallback(() => {
        switch (sortState) {
          case 'one':
            return 'ONE';
          case 'two':
            return 'TWO';
          case 'three':
            return 'THREE';
          case 'four':
            return 'FOUR';
          default:
            return 'ONE';
        }
      }, [sortState]);

This is to be used inside the jsx

<div>Sort:{renderContent()}</div>

2 Comments

Wrapping it in a useCallback does nothing useful here. It only adds overhead.
it should be wrapped in a useMemo so the returned component reference is the same.
2

Here is a full working example using a button to switch between components

you can set a constructor as following

constructor(props)
{
    super(props);
    this.state={
        currentView: ''
    }
}

then you can render components as following

  render() 
{
    const switchView = () => {

    switch(this.state.currentView) 
    {

      case "settings":   return <h2>settings</h2>;
      case "dashboard":   return <h2>dashboard</h2>;

      default:      return <h2>dashboard</h2>
    }
  }

    return (

       <div>

            <button onClick={(e) => this.setState({currentView: "settings"})}>settings</button>
            <button onClick={(e) => this.setState({currentView: "dashboard"})}>dashboard</button>

            <div className="container">
                { switchView() }
            </div>


        </div>
    );
}

}

As you can see I am using a button to switch between states.

Comments

2

I know I'm a bit late to the party, but I think this implementation might help

You can render the components using conditional operators instead

If you had the following switch statement

switch(value) {
    case CASE1:
        return <Case1Component/>

    case CASE2:
        return <Case2Component/>

    case CASE3:
        return <Case3Component/>

    default:
        return <DefaultComponent/>
}

You can convert it to react component like so

const cases = [CASE0, CASE1, CASE2]
// Reminds me of 'react-router-dom'
return (
    <div>
        {value === cases[0] && <Case0Component/>}
        {value === cases[1] && <Case1Component/>}
        {value === cases[2] && <Case2Component/>}
        {!cases.includes(value) && <DefaultComponent/>}
    </div>
)

1 Comment

This works but it will check each one of them even when first(or any) is found, it will keep running === statement.
2

To expand on @lenkan's answer:

You can do this type-safely, too. It isn't pretty if you wanna do it inline, but it works perfectly fine.

{
    ({
        [FooBar.FOO]: <Foo />,
        [FooBar.BAR]: <Bar />
    } satisfies Record<FooBar, ReactNode>)[fooBar]
}

You can wrap it in Partial<> if you wanna make the cases optional.

Or use { [key in FooBar]?: ReactNode } instead of Partial<Record<FooBar, ReactNode>>. (With, or without the ?)

I would definitely move the switch "cases" to a const though if you have anything more complicated, though. You can do a lot with it.

enum FooBar {
    FOO = 'foo',
    BAR = 'bar',
}

const switchFooBar = {
    [FooBar.FOO]: (({ howFooBar }) => <span>{howFooBar || ''}foo</span>) as React.FC<{ howFooBar?: string }>,
    [FooBar.BAR]: ({ children }) => <div>{children}</div>,
} satisfies { [key in FooBar]?: React.FC<any> };

return <>
    {switchFooBar[fooBar]({ children: <span>bar</span> })}
    <switchFooBar.foo howFooBar="very" />
</>

Comments

1

I am using this helper that allows me to have switch statements in JSX

// in helpers folder
const switchTrue = (object) => {
  const { default: defaultValue, ...rest } = object;
  const obj = { default: defaultValue, ...rest };
  const result = Object.keys(obj).reduce((acc, cur) => {
    return {
      ...acc,
      [cur === 'default' ? 'true' : cur]: obj[cur],
    };
  }, {});
  return result['true'];
};

const Sample = () => {
  const isDataLoading = false;
  return (
    <div>
      {
        switchTrue({
          [`${isDataLoading}`]: <div>Loading</div>,
          [`${!isDataLoading}`]: <div>Data Ready</div>,
          default: <div>Default</div>,
        })
      }
    </div>
  )
}

ReactDOM.render(
  <Sample/>,
  document.getElementById("react")
);
<script src="https://cdnjs.cloudflare.com/ajax/libs/react/16.6.3/umd/react.production.min.js"></script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/react-dom/16.6.3/umd/react-dom.production.min.js"></script>
<div id="react"></div>

Comments

1

This helper should do the trick.

Example Usage:

{componentSwitch(3, (switcher => switcher
    .case(1, () =>
        <p>It is one</p>
    )
    .case(2, () =>
        <p>It is two</p>
    )
    .default(() =>
        <p>It is something different</p>
    )
))}

Helper:

interface SwitchCases<T> {
    case: (value: T, result: () => React.ReactNode) => SwitchCases<T>;
    default: (result: () => React.ReactNode) => SwitchCases<T>;
}

export function componentSwitch<T>(value: T, cases: (cases: SwitchCases<T>) => void) {

    var possibleCases: { value: T, result: () => React.ReactNode }[] = [];
    var defaultResult: (() => React.ReactNode) | null = null;

    var getSwitchCases: () => SwitchCases<T> = () => ({
        case: (value: T, result: () => React.ReactNode) => {
            possibleCases.push({ value: value, result });

            return getSwitchCases();
        },
        default: (result: () => React.ReactNode) => {
            defaultResult = result;

            return getSwitchCases();
        },
    })
    
    // getSwitchCases is recursive and will add all possible cases to the possibleCases array and sets defaultResult.
    cases(getSwitchCases());

    // Check if one of the cases is met
    for(const possibleCase of possibleCases) {
        if (possibleCase.value === value) {
            return possibleCase.result();
        }
    }

    // Check if the default case is defined
    if (defaultResult) {
        // Typescript wrongly assumes that defaultResult is always null.
        var fixedDefaultResult = defaultResult as (() => React.ReactNode);

        return fixedDefaultResult();
    }

    // None of the cases were met and default was not defined.
    return undefined;
}

Comments

1

Is easy my example in typescrip, change page on object in state

// add names of pages (safe) or change to string (unsafe)
type pages = 'bip' | 'boop'

const App = (params: params) => {

     
    const [menu, setMenu] = useState<pages>("bip")

    const handleOnClick = (value: string) => setMenu(value);

    const pages: { [key: string]: React.ReactNode } = {
        bip: <div>bip</div>,
        boop: <div>Boop</div>
    }

    return (
        <>

            {pages[menu] ? pages[menu] : <DefaultComponent/>}

            <OtherComponent onClick={handleOnClick} />

        </>
    );
};

export default App;

Comments

0

This answer is specifically intended to address this "duplicate" question, by @tonyfat, regarding how to use conditional expressions to handle the same task.


Avoiding statements here seems like more trouble than it's worth, but this script does the job as the snippet demonstrates:

// Runs tests
let id = 0, flag = 0;
renderByFlag(id, flag); // jobId out of range

id = 1; // jobId in range
while(++flag < 5){ // active flag ranges from 1 to 4
  renderByFlag(id, flag);
}

// Defines a function that chooses what to render based on two provided values
function renderByFlag(jobId, activeFlag){
  jobId === 1 ? (
      activeFlag === 1
        ? render("A (flag = 1)")
        : activeFlag === 2
          ? render("B (flag = 2)")
          : activeFlag === 3
            ? render("C (flag = 3)")
            : pass(`flag ${activeFlag} out of range`)
  )
  : pass(`jobId ${jobId} out of range`)
}

// Defines logging functions for demo purposes
function render(val){ console.log(`Rendering ${val}`); }
function pass(reason){ console.log(`Doing nothing (${reason})`) }

2 Comments

i agree this is a much better and cleaner syntactically also you can just use comments in case the naming/convention is not very clear.
least legible option
-3

This is another approach.

render() {
   return {this[`renderStep${this.state.step}`]()}

renderStep0() { return 'step 0' }
renderStep1() { return 'step 1' }

Comments

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.