Could put a redirect on the /edituser route if a cookie is not present, currently it returns the heroku error page.

The place it says "I dont like coffee" delete my username and message. could be named differently

It's fantastic that you've not only handled this error, but you've sent a useful error message back to the user and even provided them with a quick action to take.

My only issue is that the "Go back" button should really just be a link. It's a navigation action ("view this page") rather than submitting any user data to the server. Always prefer the simplest solution you can.

Also POST requests generally shouldn't return HTML responses—it's better for form submissions to redirect to a new page so you get a fresh GET request. Otherwise you get problems like users refreshing the response page (or clicking back to it later) and resubmitting the form by accident. Also generally browsers do things like cache GET responses (since they should be safe). They cannot do this for POSTs since they are designed to change things on the server.

Desktop: 💯 % Performance, Best Practice & SEO 🥳 , 90% Accessibility 👍🏾

Accessibility

• Background and foreground colors do not have a sufficient contrast ratio.Read more

• List items (<li>) are not contained within <ul> or <ol> parent elements. Read more

Mobile: 98% Performance, 💯 % Best Practice 🥳 & 96% SEO , 90% Accessibility 👍🏾

SEO

• Tap targets are not sized appropriately 67% appropriately sized tap targets.
  Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more.

• ideas from Tuesday-morning workshop: Session management
• .env files
• update .gitignore

🤷‍♂️

• deploy simple "Hello"
• set up database
• deploy advanced: with working database, what about .env?

All the E1 A2 labels plus when the start times work really well. 👏 Inspiring

I like the simplistic layout of the cade and how it functions. it is easy to follow

You have a really good lighthouse accessibility score of 93 💡

The only minor issue was that: 'List items (<li>) are not contained within <ul> or <ol> parent elements.'

This means that screen readers would not announce them properly

Really like your detailed Readme file with all your co-authors, project role, mistaked, links.
Next time maybe add some screenshots of your app and instructions on how to run your repo locally.

I know your probably didn't have time, but try to remove any unused commented out code and console.logs

Love your coffee theme, app name and colour. Looks very stylish and professional.
The only improvement is to make it more responsive for mobile view, as names get mixed up.

Good testing methods for running the tests on cypress.

• Sign up
• Log in
• Write a coffee wish

All:

• Authentication: cookie, hash, SQL
• HTML: semantic, label
• requirements
• eventListeners
• error: function, HTML field, css class .error

I'm pretty sure this can be done will all of our sites, but could be cool to put some pattern that prevents it?

Great page, well done 😎

An improvement could be to tell the user the required length of the password before they attempt to sign up

Name could have a character limit in the form to stop mega long names breaking the page layout

• ESLint
• Cypress
• Node.js, Express, Nodemon
• Database
• Cookies
• Encrypt

I tried to access your schema for the project on MIRO, but access was denied.

I really like your project board! Especially the 'Try again later' tab. Look really organised ☕

Your tests are not running because when you start running your tests, Cypress does not know the url of the app you plan to test. So, Cypress initially opens on https://localhost + a random port.

As soon as it encounters acy.visit(), Cypress then switches to the url of the main window to the url specified in your visit. This can result in a 'flash' or 'reload' when your tests first start.

By setting the baseUrl, you can avoid this reload altogether. Cypress will load the main window in the baseUrl you specified as soon as your tests start.

• You are missing

{
  "baseUrl": "http://localhost:3000"
}

You will find more information in the cypress docs

Great to see that you have used Miro board for visualising and created Hackmd with all the setup instructions. This will save you lot of time in the future projects.

Liked the readme files, highlighted problems when it came to heroku which we found usefull

• .catch
• Customise "Sorry" messages
• final catch-all in server.js

Well done in hosting your project on Heroku! 🥳
I was able to sign up and see my order as well as delete it and had errors handled with user not found! 👏🏾
Also excellent work as you were able to to velocity & actuals! This will help you manage your time in the up coming weeks.
Well done in co-authoring, and getting your commits near enough even.
Your code is modularised and you managed to get some cypress tests done!
Pat your selves on the back!

• ? preset coffee options?
• tables, columns, constraints
• try INSERT, SELECT
• connect Heroku database
  • Connect to your Heroku database with psql your_heroku_database_url
  • Insert the data into your DB with \i init.sql

• get
• post, auth, model
• encrypt password
• create long sid

Hi team! Very impressed with all your hard work and how nice your project looks and it works and you managed to deploy it! You improved your database skills and learned so much during this week and you should be very proud of yourself!

• bla

You successfully managed to implement sign up/log in/sign out and even update the user details. That was the main goal for this project and you achieved it, it all works! Your code looks clean, readable and modularised.
And you even had time for all the tests! Well done!