{"id":15,"date":"2023-02-10T00:56:26","date_gmt":"2023-02-10T00:56:26","guid":{"rendered":"https:\/\/blogs.oregonstate.edu\/philpeiffer\/?p=15"},"modified":"2023-02-10T00:56:26","modified_gmt":"2023-02-10T00:56:26","slug":"conditional-rendering-in-react","status":"publish","type":"post","link":"https:\/\/blogs.oregonstate.edu\/philpeiffer\/2023\/02\/10\/conditional-rendering-in-react\/","title":{"rendered":"Conditional Rendering in React"},"content":{"rendered":"\n

I started this week wanting to do something fairly simple. Like almost anything with CS, I began by thinking “It can’t be that hard”. Three days later, and I finally figured it out.<\/p>\n\n\n\n

What Am I Doing?<\/h3>\n\n\n\n

I’m building a React application as part of my capstone project. The React project is build right now so that when a user wants to see something related to their contacts or skills, they do so by navigating between various “pages” through a react-router. This is fine for MVP type stuff, but this is capstone, right? Shouldn’t we have a more polished and professional presentation? I thought so, so my idea was to load this info in a “feature-pane” that slides out on the right hand side. <\/p>\n\n\n\n

My vision was this: a user has a main homepage that displays an overview of their data. When they want to edit some part of that data, they click on it in the homepage. After clicking, a window would slide out from the right that would contain detailed information about that specific piece of data. The user could edit it in this window and hit “submit”, and then the window would slide back and become hidden again.<\/p>\n\n\n\n

My Approach<\/h3>\n\n\n\n

The figure below gives you an idea of how our App is structured currently. You’ll see that we have a top level div<\/code>, under this we have a header, a navigation bar, and then we finally get to our main<\/code> content. The main<\/code> area is where our pages load when different routes are visited. We’re not actually visiting new pages with these routes, we’re just replacing what’s in the DOM with these React functional components. So anyways, my two main questions at this point were – 1) where do I put the hidden window, and 2) how do I make it so that this window slides out from the right and<\/strong> overlays the current window (i.e. everything doesn’t slide around when it pops out)?<\/p>\n\n\n\n

\"\"
Starting point of application structure.<\/figcaption><\/figure>\n\n\n\n

I’m going to start with #2. Some quick googling found some tips around CSS animations. Basically, what you do is, on the component that you want to slide in\/out, you create a class name that’s unique to that component. From there, I defined that class in CSS as having the following properties:<\/p>\n\n\n

\n
\"\"
CSS properties of the sliding window.<\/figcaption><\/figure>\n<\/div>\n\n\n

The definitions are pretty self explanatory, but the important ones with regard to animation are animation-duration<\/code>, and animation-name<\/code>. The animation-name<\/code> property is then tied to a CSS keyframe, which defines aspects of the animation. There are a lot of in-depth explanations floating around online, but here’s how I defined my CSS keyframe. Note that the @keyframe<\/code> is followed by the animation-name.<\/p>\n\n\n

\n
\"\"
The keyframe that defines the animation over time.<\/figcaption><\/figure>\n<\/div>\n\n\n

The phrases from<\/code> and to<\/code> in the keyframe are short for time=0s<\/code> to time=end<\/code>. So basically, at time = 0s, the margin-left of the component with the animation is at 100%. This means that the component will be off screen right. Great, now at time = end, the margin-left will be at 0%, meaning the component will be visible. <\/p>\n\n\n\n

I still had to figure out how to get it so that it looked like the window was above the rest of the screen, however. To do this, I started looking into stacked contexts in CSS. To create a stacking context, you need to have positioning of your page elements be something other than static<\/code> (the default). MDN has a great article for understanding the details, but the main thing to take away is that stacking doesn’t work out of the box. You have to intentionally define positioning for it to work. You can see in the CSS clip above that I chose absolute<\/code>, which means that my component will be positioned at the exact coordinates that I pass it. What are those coordinates in reference to though? Great question, the coordinates that you pass it are from its closest positioned ancestor<\/strong>. It’s confusing, I know.<\/p>\n\n\n\n

It took me a while to figure out what this meant and the subtle implications that it has. Basically, if you have something like this:<\/p>\n\n\n

\n
\"\"
Demo of stacking<\/figcaption><\/figure>\n<\/div>\n\n\n

Then when you try to position your “stacker”, the position isn’t going to be from the top left corner of the parent container. Instead, it’s going to be from the top left corner of the grandparent container. This is because the grandparent is the first ancestor that doesn’t have a position of static<\/code>. In other words, it was the first ancestor that was deliberately placed on the page. Therefore, the CSS developers decided that this should be your reference point when passing coordinates for positioning. It makes sense once you see it in this light.<\/p>\n\n\n\n

Once I understood this, then it was a matter of laying out my components properly so that my sliding container’s parent was the top level div<\/code>. The top level div<\/code> is the first element to be positioned, so my positioning of the sliding pane would be with respect to the top left corner of the screen. This is the answer to #1!<\/p>\n\n\n\n

I still have some more to go on #2 though. Now the question became, how do I toggle this slider? If I were to just slap that class on the slider component, then every time I loaded the App the slider would slide on out. This isn’t what I wanted. Instead, I wanted it to remain hidden until I clicked something.<\/p>\n\n\n\n

Enter Conditional Rendering<\/h3>\n\n\n\n

This isn’t really conditional rendering per-se. Instead, it’s using state in the component to control the class name that’s given to a JSX element. What I decided to do was use the useState<\/code> hook in React to store my class name, and give it an initial value of “hidden”.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

I then injected that value of state into my JSX element like so: <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Using useState<\/code> means that I can change that class name to whatever I wanted throughout my app by calling the setter function that’s returned from useState<\/code>. <\/p>\n\n\n\n

By doing it this way I can pass the setter function to various components in my app. Then, when I want to change the class name I can simply call the setter and pass a new class name. This will re-render the App and change the class name, which if the class name matches feature-pane<\/code> will trigger the animation. <\/p>\n\n\n\n

Conclusion<\/h2>\n\n\n\n

That was a wild ride, and it took a lot of trial and error to figure out exactly how to get it done. Here’s what the final code looks like, you’ll notice that I put the feature-pane right underneath the top most div<\/code>, so that my positioning is correct:<\/p>\n\n\n\n

\"\"
The final result after adding the sliding feature.<\/figcaption><\/figure>\n\n\n\n

There’s still one more gotcha that I didn’t explain that has to do with how you set your display in CSS on the initial class. You have to use hidden<\/code> or else you’ll encounter a strange flash of a component that then disappears right before starting to slide out from the left. I’ll leave it to you to figure out why this is occurring because I think we learn the best by troubleshooting issues. It’s a pretty easy issue to figure out once you understand the mechanics. In any case, I hope that you enjoyed learning this with me.<\/p>\n","protected":false},"excerpt":{"rendered":"

I started this week wanting to do something fairly simple. Like almost anything with CS, I began by thinking “It can’t be that hard”. Three days later, and I finally figured it out. What Am I Doing? I’m building a React application as part of my capstone project. The React project is build right now … Continue reading Conditional Rendering in React<\/span><\/a><\/p>\n","protected":false},"author":13144,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-15","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/blogs.oregonstate.edu\/philpeiffer\/wp-json\/wp\/v2\/posts\/15","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.oregonstate.edu\/philpeiffer\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.oregonstate.edu\/philpeiffer\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/philpeiffer\/wp-json\/wp\/v2\/users\/13144"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/philpeiffer\/wp-json\/wp\/v2\/comments?post=15"}],"version-history":[{"count":3,"href":"https:\/\/blogs.oregonstate.edu\/philpeiffer\/wp-json\/wp\/v2\/posts\/15\/revisions"}],"predecessor-version":[{"id":25,"href":"https:\/\/blogs.oregonstate.edu\/philpeiffer\/wp-json\/wp\/v2\/posts\/15\/revisions\/25"}],"wp:attachment":[{"href":"https:\/\/blogs.oregonstate.edu\/philpeiffer\/wp-json\/wp\/v2\/media?parent=15"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/philpeiffer\/wp-json\/wp\/v2\/categories?post=15"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.oregonstate.edu\/philpeiffer\/wp-json\/wp\/v2\/tags?post=15"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}