You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use each to return an array with all of the elements from the numbers array that have two or more digits.
Refactor the code you implemented for #1 above to use find_all instead of each.
Use each to find all of the elements from the numbers array whose squares are odd. (Example: 5 would be returned because 5^2 = 25 and 25 is odd. 10 would not be returned because 10^2 is 100 and 100 is even.
Refactor the code you implemented for #3 above to use find_all instead of each.
For this challenge, you will be refactoring your Viewing Party Lite project to include basic authentication. Currently on your Viewing Party Lite project, a user 'registers' by providing their name and email. We want to update the registration form to include a password and a password confirmation field, and we want to securely store that user's password upon registration.If you would prefer to not use your own repo for this challenge, you can use this repo instead.
User Story #1 - Registration (w/ Authentication) Happy Path
For this challenge, focus on using Behavior Driven Development (BDD) over Test Driven Development (TDD). As a reminder, if you'd prefer to use this repo instead of your own project, that's fine. Just switch to the authentication branch and build off of that code.
Part 1: Sessions Challenge
Task 1: Remember a user upon successful log in/registration
In your users#create action, and your users#login_user (or sessions#create if you've refactored) action, add that authenticated users id into the session session[:user_id] = user.id
Consuming APIs Practice -- This practice focuses on the process of making a Faraday connection, and getting data from APIs. Specifically, it works on creating services.
Parks Finder -- Although this is prep for the mid mod, the mid mod will also be on consuming APIs. Y’all just got some practice with that this week! So, believe it or not, you’re ready to put those skills back into action with this practice mid mod.
Prep for Week 2:
Review Namespacing -- As you get into your next project, namespacing will become handy. Take some time this weekend to review Namespacing and why it's used.
AR challenge - If you did not get to finish the AR review and try out the AR challenge, please find time this weekend to do just that. Directions are linked in the calendar event from Friday.
With any feedback you got on Rails Engine Lite, refactor your project. You can send Dani and myself a link to your repo, and tell us where to look, and we can get you more feedback sometime next week.
Students and Cohorts API - Building an API practice (beginner to mid level of difficulty), directions are in readme. Here is a review of this challenge.
Review your Viewing Party Projects -- we will look at them again on Monday.
Get on the zoom call and instruct anyone who would like to pitch an idea to raise their hands. Some students will have huge presentations, which deter other students to present if they only have a half-baked idea. Encourage students that anyone can pitch even if they don’t have all the details figured out. (you might need to wait awhile).
Call on students one by one to present. After they’re done presenting, open it up for any follow up questions (either by yourself or students). When students are done presenting, remind them to fill out the survey that’s linked in the calendar event.
After everyone pitches their ideas, hop off the call and edit their first surveyto include all of the names of the apps that were pitched.
Send out the survey ASAP and tell students that they have until whatever time, to select the 5 that they want their cohort to create.
Collect answers when time is up, and update [this form](https://