Tony😋
Christine😉
Gigi😌
Francesca😀

Our aim was to build a simple postcode autocomplete app using Node.JS, HTML and CSS.

1. Our focus this week is on everyone learning the most rather than having the most fabulous project
2. Pair programming - ensure everyone pairs up with everyone at least once
3. Use 20/20/20 - if a pair has not found an answer after 20 min we can open the problem up to the team and do a mob

1. We use an autocomplete API link

2. Autocomplete dropdown: https://www.w3schools.com/howto/howto_js_autocomplete.asp

3. Listen to input value change: https://stackoverflow.com/questions/26946235/pure-javascript-listen-to-input-value-change

4. Initially we set up a dummy JSON file and made an API call from the client side to our own backend dummy data. This was successful, however we were unable to make an API call from our server to the Postcodes API, hence we just enhanced our app by making the API call from client side to the Postcodes API.

• Deploy to Heroku as a group (+ link to our repos)
• App architecture mock up
• Set up skeleton files
• Agree on file structure for server side code

• Decide on new task list + distribute to pairs
• Access object from server side and populate dom dropdown
  • Event listener on key_press and re query the object
  • Use query string to to concatante to longer query string and parse in order to return updated object data (irrelevant as inconsistent with app architecture)
• Create pure functions + tests (irrelevant as inconsistent with app architecture)
• Create dom functions
• CSS Styling
• Put in favicon
• Ensure file structure is good and maintainable (continues to work)
• Keep an eye on Heroku deployment
• Keep Readme updated

• Website that enables users to quickly find and select words from a list of suggestions, as they type.
• The list is dynamically generated from a pre-populated list of values (i.e. a dictionary file), leveraging searching and filtering.
• A large data file is required to search through - consider the best data structure for this (e.g. .txt or .json).
• Consider how implementation affects user experience and web performance (e.g. time to load and search through the data file).

• API call to postcodes.io

• There is a HTML5 tag that is used to provide an "autocomplete" feature on elements. Users will see a drop-down list of pre-defined options as they input data. (carefull! - cant be styled) https://www.w3schools.com/tags/tag_datalist.asp

• We now understand the connection between server, router and handler functions

• How the backend and frontend communicate

• That API calls are best placed on the backend, which allows the client to continue interacting with the browser while the API makes its call

• How to deploy to Heroku!

• Listen to input value change: https://stackoverflow.com/questions/26946235/pure-javascript-listen-to-input-value-change

• How usefull mobs are with unfamiliar topics

• Making an API call from the backend is hard!

• Maximal confusion on how back and front-end communicate