See the latest project document here: MIS3502-Project-Document-V2.pdf
- put in the cityscape image
- put in the rentzen logo top left
- edit the title, footer text, name of the application in top left corner
- put in marketing fluff text
- Use http://misdemo.temple.edu/rentzen
Here’s a good username and password:
- You may need to grab more than the renterid after a successful sign in
- Improve the error messages on the client side.
- Use ajax and POST to create a login (that is, insert a record in the renters table.)
- Use ajax and PUT to update a renter profile (that is, update a record in the renters table.)
- Don’t forget to look at the “hamburger” menu in the upper right hand corner.
- Check this video: https://youtu.be/Ej3z5Sd7-G8
- Don’t forget to do your server-side error trapping. This includes using .trim() to remove leading and trailing spaces.
- Add a feature to your API to list all available rental properties in a given city. See: http://126.96.36.199:8222/
- For your reference, here is a diagram of the RentZen database schema: rentzen2019_schema.pdf
- Here are some tips on how to construct the list of rental properties: https://youtu.be/1ihzXunytaE
- BEST PRACTICE: (Server side) In your API code, every time you call the terminalWrite function, immediately follow it with a return statement. Doing this can prevent some hard-to-troubleshoot errors.
- BEST PRACTICE: (Client side) It is useful to look at both the data you send to an API as well as the data you get back. Use console.log to report on the_serialized_data you are sending and the result of the API call (both success and failure).
- BEST PRACTICE: (Client side) Make sure that the name of any input tag matches the destination column in the database. It is OK to have two html tags with the same name. However, it is bad to have two input tags with the same id. In HTML the attributes name and id serve different purposes. If you are not clear on the difference between the two, I suggest a little independent research.
- The recommended Google Street View API expects a key called “location”. The location key can accept latitude and longitude coordinates or (take note!) a street address.
- The localStorage has a method called .clear(). That could be helpful when a user logs out of the application.
- Your “add an application” feature will be easier to write if you delete one unnecessary column from the database. Here’s how: https://youtu.be/wW__FHnciBY
- This link now has all the API features that I think are necessary to complete the project. I want students to write their own version of this and not use my API endpoint. However, I thought showing a working solution would be helpful. http://188.8.131.52:8222
- I’ve notice that most students don’t appear to use http://apirequest.io to test their API code. Please, please, please give that a try. Knowing that your API code is working predictably will make you client-side work much eaasier.
- Yes, the project really is due Monday, 12/2 at 11:59 PM.