learn-co-curriculum / react-hooks-component-props-mini-project

Putting it All Together: Components and Props

Learning Goals

• Create components that return JSX
• Use props to make components dynamic
• Transform lists of data into lists of components

Overview

Now that you've learned how to work with components in React, it's time to build something and put those skills to use! Your goal for this lab is to make a static site in React to practice building components, writing JSX, and passing down data as props.

We'll be creating a personal blog site, similar to Dan Abramov's Overreacted:

There is some starter code available in src/components/App.js. There is also some data in data/blog.js that is being imported into App so you can pass it down to the components that need it.

Deliverables

Have a look at the components below and draw out a component hierarchy so you can determine how to pass data down as props.

Header

Make a Header component as a child of App. It should return:

• a <header> element with the following elements inside:
  • an <h1> with the name of the blog, passed as a prop called name

About

Make an About component as a child of App. It should return:

• an <aside> element with the following elements inside:
  • an <img> element, with the src set to an image passed as a prop called image
  • the <img> element should use this placeholder image as a default value for the prop if no prop is passed in: "https://via.placeholder.com/215"
  • the image should also be accessible! Give it an alt attribute of "blog logo"
  • a <p> element, with the text for the blog passed in as a prop called about

ArticleList

Make an ArticleList component as a child of App. It should return:

• a <main> element with the following components inside:
  • an array of Article components (one component for each of the posts passed down as props to ArticleList)
  • make sure to assign a unique key attribute to each Article

Article

Make an Article component as a child of ArticleList. It should return:

• an <article> element, with the following elements inside:
  • an <h3> element displaying the title of the article, passed as a prop called title
  • a <small> element displaying the date of the article, passed as a prop called date
    • a default value of "January 1, 1970" should be used if no date is passed as a prop
  • a <p> element displaying the preview of the article, passed as a prop called preview

Bonus Feature: 'Minutes to Read'

You'll notice in the original Overreacted site, there's a 'minutes to read' indicator next to each article.

If the article takes less than 30 minutes to read:

• For every 5 minutes (rounded up to the nearest 5), display a coffee cup emoji. For example, if the article takes 3 minutes to read, you should display "☕️ 3 min read". If the article takes 7 minute, you should display "☕️☕️ 7 min read".

If the article takes 30 minutes or longer to read:

• For every 10 minutes (rounded up to the nearest 10), display a bento box emoji. For example, if the article takes 35 minutes to read, you should display "🍱🍱🍱🍱 35 min read". If the article takes 61 minutes to read, you should display "🍱🍱🍱🍱🍱🍱🍱 61 min read".

There aren't tests for this feature, so you'll have to rely on running the code in the browser to see if your implementation works!

react-hooks-component-props-mini-project's Issues

Package.json issue

Canvas Link

https://learning.flatironschool.com/courses/6273/assignments/232346?module_item_id=544471

Concern

These lines in package.json are the incorrect syntax and cause the test not to run .

"jest": {
"transform": {
"^.+\.js$": "babel-jest",
"^.+\.svg$": "jest-svg-transformer"
}
},

Additional Context

Instructor Antonio is DOPE

Suggested Changes

removing the above lines causes the test to run properly.

Please Consider Renaming 'Article' And 'ArticleList' To 'Post' And 'PostList'

Canvas Link

https://learning.flatironschool.com/courses/5285/assignments/172447?module_item_id=376309

Concern

The following should be revised for this lesson:
'Article' and 'ArticleList' components should be renamed to 'Post' and 'PostList'.

This is because this is a blog website with posts, and not academic articles. The context with the naming is weird, and would be easier if this was just renamed accordingly.

Additional Context

No response

Suggested Changes

Mentioned above ^

Update README to be more clear on prop naming expectations

Canvas Link

https://learning.flatironschool.com/courses/5842/assignments/214265

Concern

In the deliverables, the expected name of the prop is italicized but I think it should be made more clear that they need to name the props correctly or they will not pass the tests. For example, change the first deliverable from
an <h1> with the _name_ of the blog, passed as a prop to
an <h1> with the name of the blog, passed as a prop called name

It is currently not clear enough and the error messages that are returned from learn test when their code works but they're just naming their props incorrectly is not helpful to the student. I.E.: I changed the prop name "posts" to "articles" (Which I have seen multiple students do) but this is the error they get from learn test:

This is confusing for students because their articles are rendering just fine but the test is not passing. It is difficult for students to look at this error and understand that they just need to rename articles to posts to get their tests passing.

Additional Context

Since codegrade will require all tests to pass before they can submit the assignment, I highly recommend making this change before phase two when codegrade is live with students.

Suggested Changes

No response

Typo of props for ArticleList

Canvas Link

https://learning.flatironschool.com/courses/6383/assignments/235196?module_item_id=551844

Concern

In the instructions for ArticleList, it is stated that the props passed down to ArticleList will be post (singular): an array of Article components (one component for each post passed down as a prop called post to ArticleList).

However, the tests for this lab make clear that ArticleTest will be tested with a prop called posts (plural):

test("renders a <main> element", () => {
  const { container } = render(<ArticleList posts={posts} />);
  expect(container.querySelector("main")).toBeInTheDocument();
});

Given that the prop is an array, the plural form makes more sense, and I think it would be clearer if it were referred to as such in the instructions.

Additional Context

I paired with a Technical Coach who agreed that this seemed like a typo in the instructions, and suggested I flag the issue here.

Suggested Changes

Just a typo change--changing "post" to "posts" in the instructions would suffice, I think!