FAQ: Container Components From Presentational Components - Separate Container Components From Presentational Components: Apply

This community-built FAQ covers the “Separate Container Components From Presentational Components: Apply” exercise from the lesson “Container Components From Presentational Components”.

Paths and Courses
This exercise can be found in the following Codecademy content:

Web Development

Learn ReactJS: Part II

FAQs on the exercise Separate Container Components From Presentational Components: Apply

Join the Discussion. Help a fellow learner on their journey.

Ask or answer a question about this exercise by clicking reply (reply) below!

Agree with a comment or answer? Like (like) to up-vote the contribution!

Need broader help or resources? Head here.

Looking for motivation to keep learning? Join our wider discussions.

Learn more about how to use this guide.

Found a bug? Report it!

Have a question about your account or billing? Reach out to our customer support team!

None of the above? Find out where to ask other questions here!

A question on a convention I noticed. I typically do not add a space within the curly brackets on named import statements, but noticed that this seems to be pretty common here in the lessons. For example:

What I normally do:

import {thing} from './thing';

What I see here a lot:

import { thing } from './thing';

While there was no difference in functionality that I could observe, I wanted to know if there are cases where this would matter such that following the convention would prevent possible inadvertent bugs in the future.