Currently, URLookup doesn't use any fancy state management. The search input state is being handled in App.js so that the data can be passed to the Results component as props. Thus, the Search component defined in "/client/src/components/Search.js" is not being used because it can't pass the state data directly to the Results component since they are sibling components.
Thus, to break the front-end down further into components, state needs to be managed using Redux or React Context API.
Currently, URLookup doesn't use any fancy state management. The search input state is being handled in App.js so that the data can be passed to the Results component as props. Thus, the Search component defined in "/client/src/components/Search.js" is not being used because it can't pass the state data directly to the Results component since they are sibling components.
Thus, to break the front-end down further into components, state needs to be managed using Redux or React Context API.