Early Returns in React Components

> When and how should you return early in a React component?
Cover Image for Early Returns in React Components

In continuation from my post on JSS project tips, I want to cover early returns in React components. When building a component, one must always ask, "under what conditions would this component not be displayed?"

For example:

  • Required field data is not present
  • Datasource item is null
  • No results were returned from a query / search
  • Page is in or not in edit mode
  • User is not authorized to view the component

It's one thing to ask the question, but it's another to implement properly.

What Not to Do

I was recently looking at a NextJS/JS headless build and noticed this check in a component prior to rendering the markup:


_9
if (!data) {
_9
return;
_9
}
_9
_9
return (
_9
<>
_9
<div>{data}</div>
_9
</>
_9
)

This will return an error message:

Nothing was returned from render. This usually means a return statement is missing. Or, to render nothing, return null.

Had this been written in TypeScript, the error would have been caught at compile time.

Return Types

Realistically speaking, I could imagine a developer performing an early return with any of these values:


_13
// Don't do this
_13
return; // Will throw an error -- this is the same as returning undefined
_13
return undefined; // Will throw an error
_13
return '';
_13
_13
// This is the equivalent of rendering nothing and is ok
_13
return false;
_13
return null;
_13
_13
// These may be useful in certain scenarios
_13
return <div></div>;
_13
// This <></> syntax is called React Fragments. In this specific example, we're returning an empty fragment, which is equivalent to rendering nothing.
_13
return <></>;

Conclusion

Always ask under what conditions a component should not render, or under which conditions some or all of the elements within it should be hidden. React components expect you to return elements, null, or false. As always, when you are working on early returns, be sure to test in EE!

Keep learning,

MG


More Stories

Cover Image for Ideas For Docker up.ps1 Scripts

Ideas For Docker up.ps1 Scripts

> Because Docker can be brittle

Cover Image for JSS: Reducing Bloat in Multilist Field Serialization

JSS: Reducing Bloat in Multilist Field Serialization

> Because: performance, security, and error-avoidance

Cover Image for How to Run Old Versions of Solr in a Docker Container

How to Run Old Versions of Solr in a Docker Container

> Please don't make me install another version of Solr on my local...

Cover Image for Script: Boost SIF Certificate Expiry Days

Script: Boost SIF Certificate Expiry Days

> One simple script that definitely won't delete your system32 folder

Cover Image for Super Fast Project Builds with Visual Studio Publish

Super Fast Project Builds with Visual Studio Publish

> For when solution builds take too long

Cover Image for Don't Ignore the HttpRequestValidationException

Don't Ignore the HttpRequestValidationException

> Doing so could be... potentially dangerous

Cover Image for Azure PaaS Cache Optimization

Azure PaaS Cache Optimization

> App Services benefit greatly from proper configuration

Cover Image for Add TypeScript Type Checks to RouteData fields

Add TypeScript Type Checks to RouteData fields

> Inspired by error: Conversion of type may be a mistake because neither type sufficiently overlaps with the other.

Cover Image for On Mentorship and Community Contributions

On Mentorship and Community Contributions

> Reflections and what I learned as an MVP mentor

Cover Image for Symposium 2022 Reflections

Symposium 2022 Reflections

> Sitecore is making big changes

Cover Image for Hello World

Hello World

> Welcome to the show

Cover Image for Tips for New Sitecore Developers

Tips for New Sitecore Developers

> Because learning Sitecore can be hard

Cover Image for Tips for Forms Implementations

Tips for Forms Implementations

> And other pro tips

Cover Image for SPE Script Performance & Troubleshooting

SPE Script Performance & Troubleshooting

> Script never ends or runs too slow? Get in here.

Cover Image for NextJS: Access has been blocked by CORS policy

NextJS: Access has been blocked by CORS policy

> CORS is almost as much of a nuisance as GDPR popups

Cover Image for NextJS/JSS Edit Frames Before JSS v21.1.0

NextJS/JSS Edit Frames Before JSS v21.1.0

> It is possible. We have the technology.

Cover Image for NextJS: Short URL for Viewing Layout Service Response

NextJS: Short URL for Viewing Layout Service Response

> Because the default URL is 2long4me

Cover Image for On Sitecore Stack Exchange (SSE)

On Sitecore Stack Exchange (SSE)

> What I've learned, what I see, what I want to see

Cover Image for Sitecore Symposium 2022

Sitecore Symposium 2022

> What I'm Watching 👀

Cover Image for Year in Review: 2022

Year in Review: 2022

> Full steam ahead

Cover Image for JSS + TypeScript Sitecore Project Tips

JSS + TypeScript Sitecore Project Tips

> New tech, new challenges

Cover Image for Tips for Applying Cumulative Sitecore XM/XP Patches and Hotfixes

Tips for Applying Cumulative Sitecore XM/XP Patches and Hotfixes

> It's probably time to overhaul your processes

Cover Image for Content Editor Search Bar Not Working

Content Editor Search Bar Not Working

> Sometimes it works, sometimes not

Cover Image for NextJS: Unable to Verify the First Certificate

NextJS: Unable to Verify the First Certificate

> UNABLE_TO_VERIFY_LEAF_SIGNATURE