dianalunaxiv / forum007 Goto Github PK

-Set up handlebars for threads in general
-Create .js file to create, update, delete threads

Some properties (display, flex-flow) that are common to sub-classes may be best used in a container class applied directly to main.handlebars.

After the merge, we'll need to make scripts to seed the database via npm run seed script in package.json.

-Some kind of alert or 404 or something should be sent back to the user stating that their username is taken or their email is already in use by another account.

-Integrate comments HTML with thread handlebars stuff
-Create .js file to post, modify/update/delete comments to backend

As far as features go, for now, we don't need a placeholder for deleted comments. However, we certainly could implement something like that.

https://dbdiagram.io/home/
Create diagram outlining data structure

Create a folder which contains the handlebars layouts and CSS.

index.html doesn't exist as a route. Instead, places which link to index.html should point to "/".

-Threads have associations with users, boards, and comment sections.
-They are contained within boards. Users create threads and comments.

-This route is for the creation of boards, which I expect will probably not be directly hit by a user.
-Boards contain threads - many threads to one board.
-These will show on the home page (possibly after login).

This is the last step of the process before we experiment with heroku. main will be our deployment branch and should be as clean and functional as possible.

Consult with the grading criteria of our project to confirm that we do indeed meet those criteria. If not, then we need to add things that qualify into our codebase.

CommentSection is redundant, I admit it! Once we get all the routes merged properly and confirmed to still be functional on working-branch, we will trim the code so that we no longer seed our database with comment section data.

-Comments are contained within comment sections. There isn't a direct relationship between individual comments and threads except through comment sections.
-They will need to be created either simultaneously with the thread, or with the creation of the first comment.

Creating a new user properly hashes a password before creation. Updating that user's password just sends the raw password to the database, and does not hash the password for some reason.

Comments in code should describe functionality where it isn't immediately obvious. We need to delete comments which have other stuff in them, like previous code or unused CSS.

-Create handlebars for user creation
-Create handlebars for viewing and updating user profile information
-Create .js files to gather data from the front end for these handlebars pages and send it to the backend

-User routes have to include some session validation, and must be hit at creation and at login.

The views and backend do not need to be deployment perfect; we just need to merge working components together to avoid conflict and divergence later down the road.

We noticed this a little last night when we were working on fireoffs. I would wager this is a problem with the way flexbox is being used in our css right now. We need to correct this.