colev1 / byob Goto Github PK

The query for concerts is currently accepting concert ids as a parameter.

Restructure the query to accept a string for the venue.

Remove 404 status code, if there are no matching concerts to the venue, the front-end should relay the info to the user. Should not be relayed through a status code.

Use TravisCI for CI

• if the test suite passes, the app should be automatically deployed to Heroku

Response to posting a new venue should have an error if the venue already exists in the database.

Data should have at least 2 different tables with at least 1 relationship (one-to-many or many-to-many)

• Postgresql database configured for development environment using knex

• Data is seeded into the database

The update concerts and update venues examples say to use the POST method, it should be PUT

Include a query parameter on at least one endpoint in order to filter the venues or concerts.

• ex: api/v1/concerts?venue=1

Create a query parameter to enable users to search for concerts by date

All endpoints should be documented including:

• what is required for that endpoint
• what the response will return if the request is successful

Write more specific setup/installation instructions for the documentation in the Readme.

There should be 4 Get Endpoints for the data

• 2 GET endpoints for all of one resource (i.e. /api/v1/venues)

• 2 GET endpoints for a specific resource (i.e. /api/v1/venues/:venue_id)

All endpoints should be tested for:

• happy path
• sad path

Configure db for testing environment using knex

Create a query parameter to allow users to search for venues by area code

Deploy BYOB to Heroku