Adding in directions progress. Users can cycle through directions one by one using 'previous' and 'next' buttons. Next steps: integrating the FourSquare API to enable real directions, setting current location as the start point, and the FourSquare location as the endpoint
Adding notes to the JS file, as well as switching the start position to the user's current position
Adding a couple more clarifying notes
Added in places model, and am able to send user's location to the server, and retrieve the FourSquare response on the front end
Added in location form to either get user's current location, or allow them to input a different one
Added in MapQuest Directions Matrix request. Need to figure out a way to make the API key secret, and how to format the venues from the FourSquare response
add geocoder gem, configure Destination model with geocoder attrs
add User model and validations
add Adventure model & controller
add basic angular file structure and empty methods for interacting with the Adventure model on the Rails back-end
add angular Destination factory and controller for user submitted destinations
add address attribute to Destination model and acceptable post params
user can submit destination and form clears after
start new Adventure form and respective controller and factory methods for submitting to the rails backend
remove Adventure zipcode attr, replace with more general location attr to allow for address input
Adding in matrix API call
add dotenv-rails gem
user can enter a start_location and time_limit and be returned walking directions to a top rated location
refine Adventure model selection methods, add new Directions factory to preserve Google Maps directions across different angular routes
add foursquare search method