Flatiron School: Trip Planner
Summary: Trip planning website with OmniAuth and User sign in
When the user goes to the Trip Planner website they first encounter the home page. The home page gives the user the option to: Sign up, Sign in locally, or Sign in with GitHub. When working on the sign in portion of the project I was able to get the local and the GitHub authenticator sign in processes to work on their own, but I kept running into issues allowing both processes to sign the user in. I made a couple silly mistakes when trying to implement the GitHub sign in portion, such as, I tried passing two arguments into .find_or_create_by() and there was another portion in the sessions_controller.rb where I was trying to authenticate the password but I was passing only params[:password] and not params[:traveler][:password] .
Once successfully logged in, the traveler is able to view the countries currently covered by the trip packages. The traveler can create a new location by entering the city and selecting one of the countries offered from a drop down list. The location will be added to the list then the traveler can select the location from the location listing and add it to their trips. The traveler can then take a look at their list of trips and also view how many trips they’ve taken on their profile page.
