Number(93).toString(2);

(Updated: )

What I did yesterday?
Getting my ass kicked by data structures

What I’m doing today?
Presenting our final project, send out contact info to cohort mates

What is blocking me?

Hello Andrew,

I’d like to keep in touch! My number is shoot me a text if you’d like! or just reply with your number :slightly_smiling_face:

Thank you!
Jack
My name is Jack and I’m a full stack developer on the metalink project
I’ll be talking about 3 things, the concert search feature and trace it starting from the front end to the back,
an item I overlooked that became an issue,
and some things that I enjoyed about working on the project. -share screen-
The concert search feature allows the user to search for metal concerts via zip code.
0
The user enters a zip code and the handleChange method on line 22 gets the value of the event target,
checks if theres already a timer running and if there is, it clears it.
Otherwise it waits a second in between changes to invoke the getConcerts method on line 28,
the getConcerts method sets the message state to loading to let the user know that data is being retrieved then
The if conditional checks the postalcode input to see if the postalcode is a valid postal code, if it is, it sends a request to our concerts api.
1
The api in index.js line 115 will then send the request parameter, in this case a zip code,
along with the genre classificationId for metal,
as well as our api key stored in our environment variable file to the ticket master api.
It does a check for valid zip code again if not valid it will return an error message to the client,
if valid it sends another fetch request to the API and package the result into the format appropriate for our front end,
which in this case would be an array of objects with the information about the event.
2
With the result returned, getConcerts will then set the concerts state on line 33 with the returned data and finally sets the loading state toggle to false message state to an empty string.
Otherwise, it sets the error message to valid us zip code to let the user know that a valid zip code is required.
This sums up the functionality of the concert search feature, and I will demonstrate what I just went through -DEMO-
3
I’ll now talk about an item I overlooked that caused an issue later in development.
This being user information wasn’t being stored properly so anything pertaining to the user would disappear on page refresh.
I fixed the page refresh by banging my head on the keyboard, a lot of research on react context/hooks then
finally figuring out to return user information via express endpoint from the back end for the current user in session when the app loads
4
Finally, My favorite part of the project was probably getting frustrated by new technology and learning about them and learning about myself in the process. I learned the different ways to persist state because I had no idea how to do it and figuring it out was pretty fun and rewarding. Also this…profile that I made for our dear friend Buhleeeyke honoring his victory over through the fire and flames by dragonforce on expert mode in guitar hero. With that I’ll pass it back over to Keith, our team lead. -END-

I was able to achieve state persistence via a call to our back end to check if there’s a current user session and if there is check against the database to pull user information when the app loads, this is on line 40 - 47 in APP and line 51 - 63

My name is Jack and I’m a full stack developer on the metalink project
I’ll be talking about the concert search feature and trace it starting from the front end to the back, some items we overlooked that became bugs, and some things that I enjoyed about working on the project. The concert search feature allows the user to search for metal concerts via zip code.

The user enters a zip code and the handleChange method on line 22 first checks if theres already a timer running and if there is, it clears it. Otherwise it waits a second in between changes to invoke the getConcerts method on line 28, the getConcerts method sets the message state to loading to let the user know that data is being retrieved and then the if conditional checks the postalcode input with regular expression to see if the postalcode is a valid postal code, if it is, it sends a request to our concerts api.

The api in index.js line 114 will then send the request parameter, in this case a zip code, the genre classificationId for metal, as well as our api key stored in our environment variable file to the ticket master api. It does a check for valid zip code again if not valid it will return an error message to the client, if valid it sends another fetch request to the API and package the result into the format appropriate for our front end, which in this case would be an array of objects with the information about the event.

With the result returned, getConcerts will then set the concerts state with the returned data and finally it sets the loading state toggle to false and sets the message state to an empty string. Otherwise, it sets the error message to valid us zip code to let the user know that a valid zip code is required. This sums up the functionality of the concert search feature.

I’ll now talk about the items I overlooked that caused an issue later in development.

My favorite part of the project was probably getting frustrated by new technology and learning about them and learning about myself in the process. I learned the different ways to persist state because I had no idea how to do it and figuring it out was pretty fun and rewarding.
With that I’ll pass it back over to Keith, our team lead.

I worked on the front and back end for User can pick from drop down, concert search and logging out features. I fixed the bug where posts from all users were showing for the current user because there was no filter to filter the returned data from the api call. Also another bug that I fixed was where the user information would disappear after page refresh, fixed it by storing state information via api call to the back end for the current user on mounting of app.
Keith ran into an issue where the chat component was calling a method to update messages in an infinite loops, I helped him fix it by using a conditional to check for state changes in the componentDidUpdate method as well as moving the getmessages method to another places where appropriate.