newtonjain/hacktheplanet

hacktheplanet's Issues

test_data builder [All Objects]

yeeeeh

check out requests.markdown on the main repo for examples of api endpoints

POST transaction [Driver]

• URL: /transaction

{
'trip_id': 123,
'driver_id': 323
}

• done
• tested

GET List of routes avail [Driver]

• URL: trip/trip//

[
{<trip_object>},
...
]

• done
• tested

Status changes on POST'ing to apis [All Users]

• When POST'ing to certain API's we need to be changing status's for the front end to know whats up
• init done
• should throw some workflow errors if you try and change the status to something that doesn't make sense
• tested

Scenic Trips [All Users] [Yelp]

• have to add multiple-destination support to the Trip model
• call Yelp api to get the best stuff around the location the Driver is

POST to trip_api is made by the Customer (the request to book the ride)

• URL: /trip/

{
<trip_object>
}

Response on 200:

{
<trip_object WITH MORE DESTINATIONS AND SHIT>
}

@theshteves you were working on this sort of, lets discuss the implementation here

GET/POST single customer/driver info [All users]

• URL: driver/<driver_id>

{
<driver_object>
}

• URL: customer/<customer_id>

{
<customer_object>
}

• done
• tested

use actual gps points instead of hardcoding

GET list of transactions [Driver]

• URL: /transactions/<driver_id>
• have no real idea what is getting passed back and forth here but i am going to guess

[
{
'driver_id:1212,
'price': 43.00
???
},
...
]

• done
• tested

more data in scenic routes

throw some more data in the scenic routes, we have it from yelp anyways

driver can choose between different routes

profile_url field for driver/customer

PATCH Trip api with the customer_id which will be on this trip [Driver]

• URL: trip/<trip_id>

(
'customer_id': <customer_id>
)

a 200 with the trip object and a changed status field will be returned on success

• new status change, done
• tested

Twillio Support [All Users]

Scenarios users will be getting texts:

GET list of customers/drivers (in area) [All Users]

• do we actually want to get drivers in the area of is returning all drivers fine for the demo @newtonjain ????? If not here is the eg.
• the object will include a random ranking
• URL: /driver/

[
{
<driver_object>
}
]

• done
• tested

support 3 drivers

POST trip [Customer]

• URL: /trip

{
<trip_object>
}

• done
• posted

Distance field on Trip model [All Users]

• be able to get the right price of the trip
• just do the straight line in between start and end addresses

• done
• tested

iframe for route preview

 <iframe width="100%" height="450" frameborder="0" style="border:0;" <!-- display: none -->
            src="https://www.google.com/maps/embed/v1/directions?key=AIzaSyCBYtphSiDRCkgJdo9y3IomkqL2ZjEi1Oc"
            + "&origin=" + "berlin"
            + "&waypoints=" + "dusseldorf"
            + "&destination=" + "munich" allowfullscreen>
    </iframe>

obviously the src tag needs to have everything in one string. I need Newton to use his angular magic to formulaic offload all of the lat-long points into the src url.

new scenic route endpoint

• returns yelp scenic locations
• two times the front end should be calling this endpoint
  • when the user presses the adventurous button
  • when the user updates the location and has the adventurous button already clicked

front end list of stuff to do

• get status changes working
• delete bad fields
• make text smaller
• show interests in list view
• one header title in profile