jemisonf / cs340_final_project Goto Github PK

Messages and comments are currently ordered by id (?), need to order by date posted instead

In api/openapi.yaml. line 285 should have msg_id instead of message_id

this section (at most 1/4 page, in prose with complete sentences) gives an overview of the miniworld (topic) of your web application. It should answer the following questions: What are you tracking in your web application, and why? Who would use it? What are the main use-cases for your application?

Start with a website map, which shows how different pages of your web application are linked from the main menu.

You can generate such a map using Microsoft Visio which is available from Microsoft under agreement with COE (Links to an external site.)Links to an external site.[onthehub.com]. Your map should list each of the web pages (or views) that your web application will have. Then, following the map, for each of the pages/views, have a page-specific section in which you explain (in prose) what the use-case for the page is, what UI components will be used, how the page will communicate with the server (e.g., HTTP GET or POST and with what parameters), and what SQL query/queries (indicate any parameters with square brackets around the parameter name, like this: SELECT * FROM Employees WHERE eid = [user_eid];) the server will execute to populate and/or respond to the page. Mock-up screen captures may be helpful to illustrate your point, for the website design part of the document

Have a basic functional Flask app up and running

Complete after #4

Authentication using a token should be added to the Flask API.
The API will have a secret file containing a list of combinations of usernames and passwords. A /login endpoint should exist that takes a JSON object containing a username and password. These values should be compared to the valid combinations in the file and, if they match an entry, the api should generate a token. The token should be added to the api's session and be sent in the response for use by the sender. Other endpoints then should first check if the supplied token matches a token in the api's session.
For simplicity, we should use the Bearer format when sending requests with a token.

Using react(?) build some static content that can be served to users

Need to allow cross site access to API

See here

• Add routes for each view
• Build React components
  • Message
  • User
  • Comment
  • Settings input
  • Followers
  • Following
  • Submit Comment
  • Submit Post
• Build async wrapper component(s)
• Build login functionality
• Create and delete message

This ticket will be to write integration tests for our Flask API. All endpoints should be tested for valid data and responses. After these are done, they should be configured to be used by CircleCI

Flask will handle API requests from the frontend, will communicate with the database, and will return JSON data back to the frontend. This issue involves writing a swagger specification for the API

Not sure exactly how to do this but it would be nice