whiteheadol / overlook Goto Github PK

• Each property and method within the user class should have appropriate tests.

• Think about where I want to do this - user class or make a new class?
• Method should be able to only show rooms with a specific roomType

• Need a method that will allow the user class to store more information about each booking. Update methods and tests accordingly.

• Deploy site on GitHub pages and update README to include new deploy link.

• Once the current user is instantiated, the screen should display all the bookings they have to their name.
• This will mean pulling in the data from the bookings API and comparing ids of user and booking.
• I want the past bookings to have an opacity to differentiate them.
• Present/future bookings will be fully solid.
• Appropriate user methods and properties to keep track of this data.

Set up basic html structure for the user dashboard.

• Is there a container to display the rooms that a user has booked?
• Is there a place to display the total amount of money a user has spent?

• On page load, the currentUser should be instantiated with their appropriate data
  • Set up a fetch call to pull this user information, but don't worry about allowing the user to choose their login information yet. Hard code a number into the url for now.
• The DOM should display welcome information with the user's name

• Write/update project readme

• When I changed my code to make it more accessibility friendly, I messed up my error message styling. Fix this!

• Double check all existing tests after slightly changing methods
• Add test(s) for the extra hotel method I built out

• Figure out what a date input will look like coming in from that field
• Build a method in user class (could consider a hotel class?) that will update an array of filtered rooms available

• At the moment, a user can attempt to book a room from the past. Add error handling so that users can only book rooms in the future.

• If no rooms match the user's filter selection, build out an error message to apologize to the user

• I deleted a redundant method in the user and hotel classes, I need to go back and delete the tests that double check these methods.

• Build in a conditional, if username includes 'customer' then do this... Can help if I get to the manager iteration
• Clicking 'submit' will check for the current user ID and update the fetch calls appropriately.
  • Plan as of now, function to change the variable equal to the user's number inside of the api calls file
  • Then, The scripts should update appropriately
  • The instantiations that are now happening on page load - tie these to the successful user login instead?
  • After the correct user is chosen, the dom updates when 'submit' is clicked as well

• Build out a room class that will store all of the information about a room.
• Build out tests that will make sure the room instances are storing the information I need.

• When I 'book' a room, I can't permanently remove it from the bookable rooms until I refresh the page.
  • I've tried refetching my bookings info and going from there with no luck, spent hours on this, got on call with my rock, she told me to not do it this way, and just build an internal method to get around it.
  • My method to work around only works until you book two different rooms on two different dates
  • How to fix?
  • Actually refetch successfully? Need more guidance - because rock, Michael, and Artan couldn't figure it out. Then, reupdate everything after refetching
  • Build a more robust method to store more information about the booked room and more effectively filter out a room that has already been booked?

• I've booked so many rooms, and there are now entire days with nothing available. Can I reset the server? How does this work? Maybe see if Artan has a tip?

• A user should be able to book a room for themselves!
• Visually, when a user clicks on a booking thumbnail, I want a small button to appear beneath the room's information that says something like 'book this room'
• Clicking this button will change the thumbnail visually, to somehow let the user know that their booking was successful
• Account for error handling by displaying a different message if they're booking didn't work
• JS Functionality will also pull room info needed from thumbnail when this button is clicked - this will get passed into our post request.
• Appropriate methods will run to update user class to include this new rooms in the rooms they've booked
• The user cost should also update
• Maybe get clarification about the posting/booking -- Should this room then be removed from the bookings API? Or is it sill available for another user to book should they log on?

• Test for both happy and sad paths

• Run through each file and check for correct spacing, indentation, and punctuation.

• When the page loads, a user should see the login page.
• Hard code these input fields in for now, and consider how I want a user to login
• Could hardcode users 1-50, but not as elegant as allowing them to type what they want and go from there?

• Once the rooms are able to be filtered by date, build out functionality that will display these filtered rooms on the DOM.
• Consider building out a 'clear filter/date/search' button that will reset everything

Set up enough css to give my project more context. No specific styling until there is more functionality in place.

• After Iteration 2, audit on both lighthouse and wave - fix site to get to 100
• Try colorblind extension
• Can I tab around my site as well?
• What about using a screen reader?
• Merge to main, but also save this branch to refer back to during final evaluation

• When the dashboard loads and the current user is instantiated, the total amount of money the user has spent should appear on the screen.
• Build out user method and properties to calculate this amount.

• Once the rooms are able to be filtered by type, build out functionality that will display these filtered rooms on the DOM.
• Consider building out a 'clear filter/date/search' button that will reset everything if haven't made already

• Test for happy and sad paths

Make a solid wireframe, laying out how I'd like the project to look and function.

• A user should be able to access this page by clicking on the 'book now' button
• When the page loads, the thumbnail area should be empty, and a date input should appear