Skip to content

Lifting State and Component Communication

In Lesson 12, Filters remembered our choices and Results remembered a selected resource. Each component could respond to its own events. Now we want those choices to affect other components: a search should change Results, and selecting a result should change Details.

Let’s look at the component that brings those pieces together. App already renders Filters, Results, and Details. It can own the information they share and pass each child what it needs. Moving state to that common parent is called lifting state up.

At the end of this class, you should be able to…

  • Identify the nearest common parent for components that need shared state.
  • Move state to that parent and pass values and callbacks through props.
  • Derive a filtered list from existing data and state.
  • Render a useful message when there is no selection or no matching result.
  • Keep local form feedback separate from shared application state.
Component Receives Reports through a callback
Filters Search text, selected categories, Open now Changes to those filter values
Results Filter values and the selected resource The resource the user selects
Details The selected resource Nothing for this activity

App will be the single source of truth for the shared values. Children render the values passed down to them and call the callbacks passed down to them. Calling a callback doesn’t bubble a custom DOM event; it’s an ordinary function call.

This follows the same communication goal as our Web Components work in Lesson 03: the result item doesn’t need to find the details panel. The parent connects them. React’s sharing state guide explains this pattern.

The search text is state. The array of resources that match that text can be calculated during rendering. Keeping another state variable for the filtered array would give us two values to keep synchronized.

For our directory, filters will apply as soon as their values change. An empty category array means All, and category names will keep the same capitalization as the source data. Our form submission will demonstrate validation separately; it won’t be required to refresh the results.


From the root of your workbook, grab today’s starter for your section. Continue with your existing copy if you’ve already downloaded it.

Terminal window
pnpm dlx tiged --disable-cache --force DG-InClass/SDEV-2150-A01-Sep-2026/sk/day-13/example/lesson-13-starter ./src/lesson-13
Terminal window
cd src/lesson-13/frontend
pnpm install
pnpm dev

The starter includes local filter state and local result selection from Lesson 12. It still uses src/data/resources.js; we don’t need the backend. Details still contains hard-coded text.

Paths below start inside src/lesson-13/frontend. Use the active JSX in App.jsx; the commented-out alternative layout can be removed.

  1. Connect Results to the parent first.

    We’ll move one piece of state at a time. Add the hook import at the top of App.jsx, then add selection state inside App.

    src/App.jsx
    import { useState } from 'react';
    import Header from './components/Header';
    src/App.jsx
    function App() {
    const [selectedResource, setSelectedResource] = useState(null);
    return (

    Pass the value and setter where Results is rendered.

    src/App.jsx
    <section className="md:col-span-2 lg:col-span-1">
    <Results />
    <Results
    selectedResource={selectedResource}
    onSelectResource={setSelectedResource}
    />
    </section>

    Now remove the duplicate state from Results and receive the two props.

    src/components/Results.jsx
    import { useState } from 'react';
    import ResultsItem from './ResultsItem';
    src/components/Results.jsx
    export default function Results() {
    const [selectedResource, setSelectedResource] = useState(null);
    export default function Results({ selectedResource, onSelectResource }) {
    return (
    src/components/Results.jsx
    location={r.location}
    onClick={() => setSelectedResource(r)}
    onClick={() => onSelectResource(r)}
    selected={selectedResource?.id === r.id}

    Select two different resources. The highlight should still move. The visible behaviour is unchanged, but App now owns the selection.

  2. Pass the selected resource to Details.

    In App.jsx, replace the unconditional Details component. With no selection, we’ll render a prompt instead.

    src/App.jsx
    <aside className="md:col-span-1 lg:col-span-1">
    <Details />
    {selectedResource ? (
    <Details resource={selectedResource} />
    ) : (
    <p className="text-sm text-base-content/70">
    Select a resource to view details.
    </p>
    )}
    </aside>

    Receive the prop in Details.

    src/components/Details.jsx
    // src/components/Details.jsx
    export default function Details() {
    export default function Details({ resource }) {
    return (

    Replace the hard-coded values in its heading and description list. Keep the existing labels and classes.

    src/components/Details.jsx
    <h2 className="text-base font-semibold text-gray-900">Peer Tutoring Centre</h2>
    <p className="text-sm text-gray-500">Drop-in tutoring and study support.</p>
    <h2 className="text-base font-semibold text-gray-900">{resource.title}</h2>
    <p className="text-sm text-gray-500">{resource.summary}</p>
    src/components/Details.jsx
    <dt className="col-span-4 font-semibold text-gray-700">Category</dt>
    <dd className="col-span-8 text-gray-600">Academic</dd>
    <dd className="col-span-8 text-gray-600">{resource.category}</dd>
    <dt className="col-span-4 font-semibold text-gray-700">Location</dt>
    <dd className="col-span-8 text-gray-600">Building W, Room W101</dd>
    <dd className="col-span-8 text-gray-600">{resource.location}</dd>
    <dt className="col-span-4 font-semibold text-gray-700">Hours</dt>
    <dd className="col-span-8 text-gray-600">Mon-Thu 10:00-16:00</dd>
    <dd className="col-span-8 text-gray-600">{resource.hours}</dd>
    <dt className="col-span-4 font-semibold text-gray-700">Contact</dt>
    <dd className="col-span-8 text-gray-600">tutoring@nait.ca</dd>
    <dd className="col-span-8 text-gray-600">{resource.contact}</dd>

    Refresh: you should see the selection prompt. Click a result: every details field should describe that resource. Copy email and Open map remain starter placeholders for now.

  3. Make result selection work with the keyboard.

    This starter attaches selection to an <li>, which isn’t a keyboard control. Move that handler onto a button inside the existing heading.

    src/components/ResultsItem.jsx
    <li onClick={onClick} className={`px-4 py-3 text-gray-900 hover:bg-gray-50 cursor-pointer ${selected ? 'bg-sky-50' : ''}`}>
    <li className={`px-4 py-3 text-gray-900 ${selected ? 'bg-sky-50' : ''}`}>
    <div className="flex items-start justify-between gap-3">
    <h2 className="text-sm font-semibold">{title}</h2>
    <h2 className="text-sm font-semibold">
    <button type="button" onClick={onClick} aria-pressed={selected}
    className="cursor-pointer rounded text-left underline-offset-2 hover:underline focus-visible:outline-2 focus-visible:outline-sky-600">
    {title}
    </button>
    </h2>

    Tab to a resource title and press Enter or Space. The same state change should update the highlight and Details.

  4. Move the three shared filter values to App.

    Add them alongside selection state.

    src/App.jsx
    function App() {
    const [selectedResource, setSelectedResource] = useState(null);
    const [searchTerm, setSearchTerm] = useState('');
    const [selectedCategories, setSelectedCategories] = useState([]);
    const [openNowOnly, setOpenNowOnly] = useState(false);

    Pass the values and callbacks to Filters.

    src/App.jsx
    <aside className="md:col-span-3 lg:col-span-1">
    <Filters />
    <Filters
    searchTerm={searchTerm}
    onSearchChange={setSearchTerm}
    selectedCategories={selectedCategories}
    onCategoryToggle={setSelectedCategories}
    openNowOnly={openNowOnly}
    onOpenNowChange={setOpenNowOnly}
    />
    </aside>

    In Filters, replace the three local declarations with props. We’ll keep useState for a local message about form submission.

    src/components/Filters.jsx
    export default function Filters() {
    const [searchTerm, setSearchTerm] = useState('');
    const [selectedCategories, setSelectedCategories] = useState([]);
    const [openNowOnly, setOpenNowOnly] = useState(false);
    export default function Filters({
    searchTerm, onSearchChange,
    selectedCategories, onCategoryToggle,
    openNowOnly, onOpenNowChange,
    }) {
    const [validationMessage, setValidationMessage] = useState('');

    Update the category handler to call the parent setter and make All clear the category array.

    src/components/Filters.jsx
    function toggleCategory(category) {
    setSelectedCategories((prev) => {
    onCategoryToggle((prev) => {
    if (category === 'All') return [];
    if (prev.includes(category)) {

    Here onCategoryToggle receives a React state setter, so it accepts an updater function. It’s a prop name we chose, not a built-in React event.

    Change the input handlers and the existing Reset handler as well.

    src/components/Filters.jsx
    onChange={(e) => setSearchTerm(e.target.value)}
    onChange={(e) => onSearchChange(e.target.value)}
    value={searchTerm}
    src/components/Filters.jsx
    checked={openNowOnly}
    onChange={(e) => setOpenNowOnly(e.target.checked)}
    onChange={(e) => onOpenNowChange(e.target.checked)}
    src/components/Filters.jsx
    onClick={() => {
    setSearchTerm('');
    setSelectedCategories([]);
    setOpenNowOnly(false);
    onSearchChange('');
    onCategoryToggle([]);
    onOpenNowChange(false);
    setValidationMessage('');
    }}

    Finally, replace the category button’s conditional class. This makes the empty-array meaning of All visible and avoids competing text colours.

    src/components/Filters.jsx
    type="button"
    className={`${selectedCategories.includes(label) && 'bg-sky-600 text-white'} rounded border border-sky-600 px-3 py-1 text-xs font-semibold text-sky-700 hover:bg-sky-50 hover:text-sky-900 focus:outline-none focus:ring-2 focus:ring-sky-200`}
    className={`btn btn-sm ${(label === 'All'
    ? selectedCategories.length === 0
    : selectedCategories.includes(label)) ? 'btn-primary' : 'btn-outline'}`}
    aria-pressed={label === 'All'
    ? selectedCategories.length === 0
    : selectedCategories.includes(label)}
    onClick={() => toggleCategory(label)}

    Try Search, categories, Open now, and Reset. They should still respond. Results hasn’t received the filters yet, so it still shows the full list.

  5. Derive the visible results.

    Pass the same three filter values to Results in App.jsx.

    src/App.jsx
    <Results
    selectedResource={selectedResource}
    onSelectResource={setSelectedResource}
    searchTerm={searchTerm}
    selectedCategories={selectedCategories}
    openNowOnly={openNowOnly}
    />

    Receive them and calculate the matching resources before returning JSX.

    src/components/Results.jsx
    export default function Results({ selectedResource, onSelectResource }) {
    export default function Results({
    selectedResource, onSelectResource,
    searchTerm, selectedCategories, openNowOnly,
    }) {
    const query = searchTerm.trim().toLowerCase();
    const filteredResources = resources.filter((resource) => {
    const matchesSearch = resource.title.toLowerCase().includes(query);
    const matchesCategory = selectedCategories.length === 0
    || selectedCategories.includes(resource.category);
    const matchesOpenNow = !openNowOnly || resource.openNow;
    return matchesSearch && matchesCategory && matchesOpenNow;
    });
    return (
    <Card title="Results">
    <p className="p-4 text-sm" role="status">
    Showing {filteredResources.length} of {resources.length} resources.
    </p>
    {filteredResources.length === 0 && (
    <p className="px-4 pb-4">No resources match. Try changing or resetting the filters.</p>
    )}
    <ul className="divide-y divide-gray-200">
    {resources.map((r) => (
    {filteredResources.map((r) => (

    Keep the rest of the list, including key={r.id}. Type part of a resource title, choose a category, and check Open now. A result must pass all three tests. With multiple categories, it can belong to any selected category.

    Try a nonsense search and then Reset. You should see the empty message followed by the full list. Selection remains independent of filtering: hiding a selected result doesn’t clear Details in this version.

  6. Give form submission a clear purpose.

    Filtering already happens while typing. We’ll use submission to check whether any filters have been chosen, with feedback inside Filters. Replace its existing handler.

    src/components/Filters.jsx
    function handleSubmit(e) {
    e.preventDefault();
    console.log('Filters submitted');
    const hasFilters = searchTerm.trim() !== ''
    || selectedCategories.length > 0 || openNowOnly;
    setValidationMessage(hasFilters
    ? 'Your filters are already applied to the results.'
    : 'Choose a filter to narrow the results. All resources are currently shown.');
    }

    Rename the submit button and add the feedback after the form’s button row.

    src/components/Filters.jsx
    Filter
    Check filters
    </button>
    src/components/Filters.jsx
    <p role="status" className="text-sm text-base-content/70">
    {validationMessage}
    </p>
    </form>

    Submit with no filters, then with a search term. The message should describe each submission. Reset should clear it. This is local feedback: Results and Details don’t need it, so there is no reason to lift it.

Trace a title click from the button to onSelectResource, through App’s setter, and back down to Details. Then trace a search change through the same pattern. There is one owner for each shared value.

Passing props through many intermediate components is often called prop drilling. Our composition only needs a few explicit connections. We’ll consider other patterns when the application needs them.


  • Add shared virtualOnly state in App. Wire the existing Virtual options checkbox through Filters, include it in Reset and form validation, and use it in Results’ filter calculation.
  • Move the no-selection message into Details. Let Details accept null, render its prompt in that case, and simplify App to always render the component.
  • Decide whether a selected resource should remain visible in Details after filters hide it. Describe your chosen behaviour before changing any code.

Check combinations, not just individual controls: Virtual options plus a category, a search with no matches, and Reset after several changes.

Continue the existing project using today’s homework.md. This time the homework deliberately uses submit-based searching: typing edits searchTerm, and submitting copies an accepted value to submittedSearchTerm. Only the submitted value filters users.

Your solution should:

  • Lift searchTerm, submittedSearchTerm, and selectedUserId into their common parent.
  • Keep UserSearch controlled through props and show an inline message for an empty or whitespace-only submission.
  • Derive the visible users from the submitted term and the visible posts from the selected user’s id.
  • Pass data and callbacks to Users and Posts, keeping stable keys and a visible selection.
  • Show helpful messages for no matches and no selected user.

Test typing before submission, submitting, selecting two different users, and getting zero matches. Document the state ownership and the distinction between typed and submitted text in your README.md. Follow the starter’s submission instructions when your checks pass.