/resources/{resource_id}

On large review template

We can use the elephantsql SQL browser (or psql) to test what commands bring back.

Currently it just says 'Hi'

Create some CSS

This is considered better practice as it is safer and the actual templates are not exposed. E.g. if you go to http://localhost:8000/views/index.hbs, you have access to the template which can be prone to injections.

You've got some hefty queries! well done on those :)

Could our project do with some refining of the file structure? We have files like reviews.js, user_reviews.js an users.js that may be better in a file?

You do it a few times, e.g. here

Just made this comment on another repo and I know you might not have covered this yet. However:

Looks like you're storing passwords in plain text and then just comparing the user input to what you have in the database when the user logs in.

This is pretty bad practice because if someone steals your database they will have all the user passwords. To prevent this you should hash and salt your passwords and never store the actual plain text password, ever.

Don't really expect you to fix this in a couple of hours code review, but maybe check out how this group did it here:
https://github.com/FAC9/the-badgerer/blob/master/src/handlers/loginHandler.js
and here:
https://github.com/FAC9/the-badgerer/blob/master/src/handlers/newUserHandler.js

Just as I've emphasised with the other teams, TESTS are just unbelievably important. Please grab me if you would like to know why.

• default
• pages
• page sections T1S
• T1 L
• T2(s/l)

Some comments.

• This should be POST. See here.
• Use template literals to construct multiline strings e.g. here.
• Can you do this with one query? If not, please make an issue explaining why.
• Apply this filter in the query.
• This should be one query (see e.g. here).

Looks really good!

• Your fonts 😄
• Filtering by reviewed resources in the main page
• Using TIMESTAMP and defaulting to CURRENT_TIMESTAMP in your SQL statements
• Modularising your JS code for getting and manipulating reviews
• Deploying an online database
• Showing a message when a guest user tries to access the 'My Reviews' page but he is not logged in.

These are optional until we have out minimal viable product up and running:

• Tape

• QUnit

• Nightwatch

• Code Climate

• CodeCov

• Travis

• Istanbul

in views/index.hbs file

It gets a bit difficult to read with this many routes in one file

env2 creates global variables, so should really be included at the root of your application, not within another module (for example what if you had environment variables which were not related to the database):

These are rendered on the server, so don't need to/shouldn't be in the public folder

• Better practice to limit database results when you query because of size and time required to make the query and then filter the results using JS.
• Instead of slicing here you could add LIMIT 8 at the end of your sql query.
• You could query the database for a specific user_id instead of filtering after you've got a big database set.
• Nice modularised structure of your JS code to get reviews and filter them though 👍