bea-ordonez / whatscookin

• 🌱 I’m currently learning React

• ⚡ Fun fact: I have four cats

My Skill Set

Frontend

Connect with me

Github Stats

Recent Blog Posts

---

Generated using Github Profilinator

whatscookin's Issues

Bug-Search - look through all views heading to and from filter view to make sure buttons pop up properly

PHASE 1 ISSUE - session storage for persistent rating

This was an extension, but we can try to set this up for next phase.

From search to everything else.......the recipes wont go away.

Build testing and class/functionality for User

Added files for the testing data, user class and the user test. Created the framework for each and need to move on to writing the tests and creating the class methods.

PHASE 1 ISSUE - Saved Recipes View (Updated 2/22) - Issue now 'bug'

This view is working as of lunchtime on 2/22 - but it is possible to add duplicate recipes to the saved recipes property of user / the global variable array. Fix is likely checking for boolean from 'savedRecipes.includes(event.target.id)' and exiting function if condition is true.

PHASE 1 ISSUE - save a recipe btn/function

This is now working - save recipe button connectivity added to event listener that was originally created for single recipe view.

Follows similar logic as single recipe view - matches the event.target.id to react to mouse click on the button, uses the id of the button to match the clicked recipe within the entire recipeData array.

Chosen Extension(Rating System)

We have chosen the rating a recipe functionality for our extension.

This is most likely going to be implemented as CSS 'after' psuedo-classing to display changes, alongside a global variable that saves the ID of each affected recipe alongside its rating out of 5 stars. - Shane

PHASE 2: Implement POST to enable saved recipe list persistence between sessions.

// This is probably going to be a new function that lives in apicalls and is imported into scripts.js

// this function should be a fetch method with the fourth endpoint as the first parameter, the second parameter will be the
// 'options object' that takes the savedRecipes array and parses it into the correct data type

Update for 2/26, Shane:

I made a POST fetch function and slopped it into scripts.js, had trouble figuring out the syntax to export two functions from apicalls so I figured we could try to get it working first then figure out the importing.

It fetches using the right syntax - as we get a message that signals a successful response according to our server files on our local server hosting repo.

The task now is to retrieve the posted data in our initial promise resolution, so that we can instantiate a User that immediately retrieves the stored data upon page load.

A11y Review - WAI ARIA and Tabbability

Review with team: how do we pass Ingredients into Recipe?

This is an actual concern that came to mind - I am fairly sure that we are building our Recipe class in a way that is not actually instantiating Ingredients and passing them into: recipe.details.ingredients.

PHASE 1 ISSUE - Search Bar Broken (Updated 2/22) *Functions but needs review for DRY*

This issue is now closer to completion - the API data is being invoked upon each search, and the display is being updated after search bar button with some success.

The 'display no results' function is no longer usable, so we will need to recreate that once we review these changes.

With team/ talk over Functionality of website for it 1.

Now that basic design is up we need to build out the beginning functionality for it 1.
Add a search bar to Nav,
Add possible tags.

Make an issue