errabun / rancid-tomatillos

Hey, I'm Eric (he/him)!

I'm a Denver, Colorado based full stack Software Developer. Check out some of the different projects that I've worked on!

You can also find me on LinkedIn

Technologies:

rancid-tomatillos's Issues

Update search method to update rendered search results as user types rather than with submit button

Iteration 5 Deliverables

• See spec for all deliverables due on Thursday 5/20
• Project should be completed by end of Monday 5/24 (aim to leave final day for polishing the project, not building out features!)

As a user, I can click the browser forward & back arrows to navigate

As a user,
When I click the forward and back arrows in a browser
Then I am taken to the previously viewed page or next page viewed in my navigation history.

Acceptance Criteria: I am able to move backwards and forwards in my navigation history.

Refactoring with Router

• refactoring our application to use Router instead of conditional rendering to change the view!
• To crete a better UX, we’re going to be using React Router to conditionally render our views based on the URL.
• All refactoring...see table in spec and add in appropriate routes
• continue to rely on your test suite to ensure that no functionality is being lost/destroyed as you add in Router!
• Look into the Cypress assertions which allow us to view our current URL pathname and add those into your tests!

As a user, I am notified when there is a network error

As a user,
When there is a 500 error
Then I see a message displayed on the page describing in user-friendly terms the reason that the page is unable to load.

Acceptance Criteria: When there is a problem with the fetch call for movie data, an error message is displayed in the browser.

As a user, I am able to navigate to homepage after viewing movie details

I am able to select a movie from the homepage of the app by clicking on the movie poster. Once the movie's details are displayed I am able to select Return Home and be redirected back to the homepage of the app where all the movies are displayed.

Acceptance Criteria: Once I am able to see all information for a selected movie, I am able to click Return Home then be redirected back to the homepage of the app where all the movies are displayed.

When the project is run locally, the terminal shows no errors and fewer than 5 warnings

As a user, I can visit the homepage

When User navigates to page, all movies are displayed for them to see.

Movies are populated with sample data at this stage.

Acceptance Criteria: When I navigate to the homepage, the window is populated with all of the movie posters.

Rubric--React Architecture

• A consistent, modular file structure is used
• A clear understanding of class components vs function components is demonstrated
• Only the data that a child component needs is passed down as props
• Logic is kept out of return statements; return statements are as readable as possible, only communicating what will be displayed
• There are some issues with the asynchronous JS where the frontend is not matching with the backend
• There are multiple functions (including fetch calls) that are doing similar pieces of functionality that could continue to be refactored
• Data fetched from API is not cleaned before being set to state

Create modular file structure

• Components directory
• Directory for each individual component
  • App, AllMovies, Movie, MovieInfo
  • Includes corresponding CSS files for each component

Testing for SearchBar

CSS style error and loading messages and search bar

Rubric--Routing

• Application uses Router to display appropriate components based on URL
• Refactoring was clean; there may be a few code smells showing the existence of the prior code, but there are no major bugs indicating a lack of understanding of Router
• Application uses React Router components and does not manipulate the history object
• UX is clear and set up so the user has access to previous routes

Add search by genre functionality

CYOA

• Review as a team what CYOA extension we would like to take on...
• See spec for list of options & word of warning!
• Once you have decided on the area to continue learning, decide on a new feature or refactor.

As a user, I can navigate to a unique URL to view movie details

As a user,
When I click on a movie and view the details for it
Then the URL updates to reflect that movie's unique ID

Acceptance Criteria: When I am viewing the details for a particular movie, the URL is updated to include the movie's unique ID

Clear input after search submit button is clicked

Network Requests & Async JS

• refactor our application to use actual data from the database (see spec for API setup and documentation)
• No other new features required; just refactoring for this iteration

Rubric--Testing

• All application views are tested
• All user flows are tested
• Happy path async functionality is stubbed and tested

As a user, I can select a movie to view its details.

From the home page of the app, I am able to click on a movie and be redirected to see only the details and information of the selected movie.

Acceptance Criteria: Given a list of movies, I am able to click on a movie poster and be redirected to see just that movies information only.

Refactor movie filtering to remove case sensitivity when searching

Rubric--Project Professionalism

• README concisely communicates the team’s individual and joint learning goals, the evolution of the project, and team member reflections while using good formatting to enhance readability
• README links to all user GitHub profiles and any applicable repos/deployed sites
• Git commits are atomic, with concise and precise descriptions of the change made
• PRs have full, consistent descriptions
  Team members do some code reviews of PRs
• Evolution of the project (decisions made, etc) is documented in the git history and PRs
• When the project is run locally, the terminal shows no errors and fewer than 5 warnings

As a user, I should be able to click a button to return to homepage if error message is displayed

If an error message is displayed, there should be a button that returns the user back to the homepage that displays all the movies.

README

• concisely communicates the team’s individual and joint learning goals, the evolution of the project, and team member reflections while using good formatting to enhance readability
• links to all user GitHub profiles and any applicable repos/deployed sites

Complete First Weekend Deliverables

• Iterations 0-3
• Project board has been updated so functionality is described as user stories
• Each user story includes thorough acceptance criteria
• Instructors have been tagged in one PR (see spec!)