Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add all project files #1

Merged
merged 15 commits into from
Jul 1, 2023
Merged

Add all project files #1

merged 15 commits into from
Jul 1, 2023

Conversation

musangamfure
Copy link
Owner

Hello,

In this PR, I have worked on all features and functionalities of the react-capstone project which in my case the Movie app.

Here are what I have done:

Home page

- When the page loads, the webapp shows the list of categories that could be filtered out by some parameter, for example by the category name.
- Along with the category name, you will display some numeric values per category that come from the API.
- When the user clicks (or taps) on a category item, the application navigates to the details page.

Details page

- In the details page, the webapp retrieves data from the API to show detailed data in the category.
- When the user clicks on the "Back" button (<), the user navigates to the home page.

Testing requirements

- Create unit tests for pure functions in your Redux code.
- Create integration tests for your application using the React Testing Library.

Technical requirements

- The project is a single-page application (SPA) built with React and Redux.
- The data retrieved from the API should be stored in the Redux store.
-  Filter shows from the API using a Filter stateless component by categories.
- Every page (the main page and the pages for each item) have a unique route within the SPA.
- The project is deployed and accessible online using [Render](https://render.com/).
- Link to the online version of the app is in the README file.

Kindly check the project and let me know what you think.

Happy Coding 🎉🎉

Copy link

@victorokoroji victorokoroji left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @musangamfure,

You have done a great job so far! 💪 👏
You still need to work on a few issues before moving on to the next project, but you're almost there!

Top highlight 🎯

  • The Pull Request is following the Git Flow ✅
  • Good redux setup✅
  • The PR title and description are professional and descriptive ✅
  • Tests well written ✅
  • Good component structure ✅
  • Linters are working properly ✅

Required Changes ♻️

  • I have gone through your code and its commendable. One major thing you need to take note is that your design doesn't match the design guideline given to you. It is very important to always stick to any design given to you and replicate it as expected. In this regard, I will like you to look critically at the design guideline and make sure to modify your design to match it for both the homepage and the details page 👎🏽

Design guideline 👇🏽
image

Check the comments under the review.

Optional suggestions

Every comment with the [OPTIONAL] prefix is not crucial enough to stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better.

You can also consider:

N/A

Cheers and Happy coding!👏👏👏

Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.

Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.


As described in the Code reviews limits policy you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.

<!-- ACKNOWLEDGEMENTS -->

## 🙏 Acknowledgments <a name="acknowledgements"></a>

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link

@codepantha codepantha left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

STATUS: CHANGES REQUIRED ♻️

Hi @musangamfure 👋,

Great work on making the changes requested by the previous reviewer 👏
You've done well implementing some of the requested changes, but there are still some which aren't addressed yet.

Highlights 🎯

✔️ Descriptive PR
✔️ Wrote unit tests 📌
✔️ Linters are passing 📌

Required Changes ♻️

Check the comments under the review.

Optional suggestions

Every comment with the [OPTIONAL] prefix won't stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better. Some of them were simply missed by the previous reviewer and addressing them will really improve your application.

Cheers and Happy coding!👏👏👏

Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.

Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.


As described in the Code reviews limits policy you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.

Comment on lines 15 to 27
<div className="show-item">
<button
type="button"
onClick={handleShowDetails}
aria-label="View more info"
className="details-btn"
>
<BsArrowRightCircle />
</button>
<img className="show-image" src={Show.image.medium} alt="" />
<h3 className="show-name">{Show.name}</h3>
<h3 className="show-rating">{Show.rating.average}</h3>
</div>

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • Please style the item cards to look exactly like the design guideline. Please follow these action steps to get a more similar design:
  1. Please use 2 background colors (a lighter and a darker variant) for the item cards and ensure that they are alternating. This will give it the look of a chequered board (like a chess board) just like in the design
  2. Style the arrow icon at the top-right of each card to look just like the one in the design
  3. Reduce the height of each card and its image so that it mirrors the cards in the design accurately.
  4. Increase the font-size of the text at the bottom of each card in order to get a more accurate design

Design Guideline

image

Your Implementation

image

Copy link

@tufoinnkuo10 tufoinnkuo10 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @musangamfure

There are some issues that you still need to work on to go to the next project but you are almost there!

To Highlight
✅ You used the correct Gitflow
✅ Descriptive pull request message
✅ linter error checks validated
✅ Test added
✅ well deployed

Required Changes ♻️
Check the comments under the review

ttt

Optional suggestions
_Every comment with the [OPTIONAL] prefix won't stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better.

Cheers and Happy coding!👏👏👏

Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.

Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.
As described in the Code reviews limits policy you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.


function ShowDetails() {
const { id } = useParams();
const shows = useSelector((state) => state.shows.Shows);

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • Wonderful job so far. Please like the previous reviewer specifically noted and as you can see from the original design, the thick and light color is in a check board form. I.e. a zigzag manner, not one side being thick color and one being lighter like in your case. Kindly use this small change as a way to advance your design skill 😄 💯
    yours

Screenshot (1183)_LI
original design
Screenshot (1092)_LI

Copy link

@tufoinnkuo10 tufoinnkuo10 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Status: Approved ✔️

Hi @musangamfure

Your project is complete! Great job for making the changes🥇. There is nothing else to say other than... it's time to merge it 🍾🚢 :shipit: . Congratulations! 🎉💯🌟

Good Points 👍

  • Descriptive Pull Request
  • Great design
  • No linter errors

Cheers..Happy coding!..and keep soaring higher! 💻 🍷 🚀

tufoin

Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.

Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.


As described in the Code reviews limits policy you have 2 more limited reviews per this project. If you think that the code review was not fair, you can request a second opinion using this form.

@musangamfure musangamfure merged commit 2b50028 into dev Jul 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants