BRANCH IS NOT NAMED ACCURATELY. Is actually for main page item retrieval/displaying + search functionality.
GETs items and displays what details we have in the database about them. Currently doesn't store: user's name (in database but a pain to get. Not done for this deliverable), date found/lost (not stored in db yet), and image (not stored in db yet).
Searches for items via SELECT .... LIKE [user input]. Updates results when user changes search bar (textInput) text.
There is a bug that appears when too few items are displayed. The entire page "flexes" towards the top, leaving a large, empty white space below the search bar. Perhaps solved by reversing flex order and changing the background color of the view/app (so that it isn't obvious that space is missing).
BRANCH IS NOT NAMED ACCURATELY. Is actually for main page item retrieval/displaying + search functionality.
GETs items and displays what details we have in the database about them. Currently doesn't store: user's name (in database but a pain to get. Not done for this deliverable), date found/lost (not stored in db yet), and image (not stored in db yet).
Searches for items via SELECT .... LIKE [user input]. Updates results when user changes search bar (textInput) text.
There is a bug that appears when too few items are displayed. The entire page "flexes" towards the top, leaving a large, empty white space below the search bar. Perhaps solved by reversing flex order and changing the background color of the view/app (so that it isn't obvious that space is missing).