prosams / 364final Goto Github PK

Final project for SI 364 IMPORTANT: This project has a .gitignore with an api key in it! It is housed in a file called goog_api_key.py. If this file is not within the rest of files, it won't work.

This project is a gas station tool with user authentication, the option to save your favorite/most used gas stations/etc to a collection that only a logged in user can see, and the option to leave anonymous ratings and comments that are visible to everyone regardless of whether they are logged in or not. You can also update ratings or delete entire entries that have been left.

routes and templates

/ — index.html

/results — results.html

/all_gas — stations.html

/all_loc — searchedlocations.html

/opinion — opinion.html

/opinionresults — opinionresults.html

/all_ops — allops.html

/login - login.html

/logout

/register - register.html

/list/ - opiniontpl.html

/update/ - update_item.html

/delete/

/create_collection - create_collection.html

/collections - collections.html

/collection/ - collection.html

Ensure that your SI364final.py file has all the setup (app.config values, import statements, code to run the app if that file is run, etc) necessary to run the Flask application, and the application runs correctly on http://localhost:5000 (and the other routes you set up). Your main file must be called SI364final.py, but of course you may include other files if you need.

A user should be able to load http://localhost:5000 and see the first page they ought to see on the application.

Include navigation in base.html with links (using a href tags) that lead to every other page in the application that a user should be able to click on. (e.g. in the lecture examples from the Feb 9 lecture, like this )

Ensure that all templates in the application inherit (using template inheritance, with extends) from base.html and include at least one additional block.

Must use user authentication (which should be based on the code you were provided to do this e.g. in HW4).

Must have data associated with a user and at least 2 routes besides logout that can only be seen by logged-in users.

At least 3 model classes besides the User class.

At least one one:many relationship that works properly built between 2 models.

At least one many:many relationship that works properly built between 2 models.

Successfully save data to each table.

Successfully query data from each of your models (so query at least one column, or all data, from every database table you have a model for) and use it to effect in the application (e.g. won't count if you make a query that has no effect on what you see, what is saved, or anything that happens in the app).

At least one query of data using an .all() method and send the results of that query to a template.

At least one query of data using a .filter_by(... and show the results of that query directly (e.g. by sending the results to a template) or indirectly (e.g. using the results of the query to make a request to an API or save other data to a table).

At least one helper function that is not a get_or_create function should be defined and invoked in the application.

At least two get_or_create functions should be defined and invoked in the application (such that information can be saved without being duplicated / encountering errors).

At least one error handler for a 404 error and a corresponding template.

Include at least 4 template .html files in addition to the error handling template files.

At least one Jinja template for loop and at least two Jinja template conditionals should occur amongst the templates.

At least one request to a REST API that is based on data submitted in a WTForm OR data accessed in another way online (e.g. scraping with BeautifulSoup that does accord with other involved sites' Terms of Service, etc).

Your application should use data from a REST API or other source such that the application processes the data in some way and saves some information that came from the source to the database (in some way).

At least one WTForm that sends data with a GET request to a new page.

At least one WTForm that sends data with a POST request to the same page. (NOT counting the login or registration forms provided for you in class.)

At least one WTForm that sends data with a POST request to a new page. (NOT counting the login or registration forms provided for you in class.)

At least two custom validators for a field in a WTForm, NOT counting the custom validators included in the log in/auth code.

Include at least one way to update items saved in the database in the application (like in HW5).

Include at least one way to delete items saved in the database in the application (also like in HW5).

Include at least one use of redirect.

Include at least two uses of url_for. (HINT: Likely you'll need to use this several times, really.)

Have at least 5 view functions that are not included with the code we have provided. (But you may have more!)