Search implementation in Remix - Mini Project: Build & Apply

Search implementation

📖 Scenario: You are building a simple search feature for a website that lists books. Users will type a search term, and the page will show only the books whose titles include that term.

🎯 Goal: Create a Remix route component that displays a list of books and filters them based on a search query typed by the user.

📋 What You'll Learn

Create an array of book objects with exact titles and ids

Add a search query string variable to hold the user's input

Filter the books array using the search query to show matching titles

Render the filtered list of books in the component

💡 Why This Matters

🌍 Real World

Search features are common on websites to help users find content quickly, such as products, articles, or books.

💼 Career

Implementing search with state and filtering is a fundamental skill for frontend developers working with React and Remix.

1

Create the books data array

Create a constant array called books with these exact objects: { id: 1, title: 'The Great Gatsby' }, { id: 2, title: 'Moby Dick' }, { id: 3, title: 'Hamlet' }.

Remix

// Create the books array with the given objects
// Your code here

Hint

Use const books = [ ... ] with the exact objects inside.

2

Add a search query state variable

Add a React state variable called searchQuery initialized to an empty string using useState.

Remix

const books = [
  { id: 1, title: 'The Great Gatsby' },
  { id: 2, title: 'Moby Dick' },
  { id: 3, title: 'Hamlet' }
];

// Add useState for searchQuery
// Your code here

Hint

Import useState and create searchQuery with useState('').

3

Filter books based on search query

Create a constant called filteredBooks that filters books to include only those where title.toLowerCase() includes searchQuery.toLowerCase().

Remix

import { useState } from 'react';

const books = [
  { id: 1, title: 'The Great Gatsby' },
  { id: 2, title: 'Moby Dick' },
  { id: 3, title: 'Hamlet' }
];

const [searchQuery, setSearchQuery] = useState('');

// Filter books by searchQuery
// Your code here

Hint

Use books.filter and check if book.title.toLowerCase() includes searchQuery.toLowerCase().

4

Render the search input and filtered list

Return JSX that includes an <input> with value={searchQuery} and onChange updating setSearchQuery, and a <ul> listing filteredBooks with each <li> showing book.title and having key={book.id}.

Remix

import { useState } from 'react';

const books = [
  { id: 1, title: 'The Great Gatsby' },
  { id: 2, title: 'Moby Dick' },
  { id: 3, title: 'Hamlet' }
];

const [searchQuery, setSearchQuery] = useState('');

const filteredBooks = books.filter(book =>
  book.title.toLowerCase().includes(searchQuery.toLowerCase())
);

// Return JSX with input and filtered list
// Your code here

Hint

Use an <input> with value and onChange to update searchQuery. Then map filteredBooks to <li> elements inside a <ul>.

Practice

1. In Remix, what is the main purpose of the loader function when implementing a search feature?

easy

A. To handle form submission events on the client side

B. To fetch and filter data based on the search query parameters

C. To style the search input and results dynamically

D. To manage user authentication during search

Solution

1. Step 1: Understand the role of the loader in Remix

   The loader runs on the server before rendering and fetches data needed for the page.

2. Step 2: Connect loader to search functionality

   When a search query is present in the URL, the loader reads it and filters data accordingly.

3. Final Answer:

   To fetch and filter data based on the search query parameters -> Option B

4. Quick Check:

   Loader fetches filtered data = A [OK]

Hint: Loader fetches data using URL query parameters [OK]

Common Mistakes:

• Thinking loader handles client-side events
• Confusing loader with styling or UI logic
• Assuming loader manages authentication

2. Which HTML form method should you use in Remix to ensure the search query appears in the URL and triggers the loader?

easy

A. DELETE

B. POST

C. PUT

D. GET

Solution

1. Step 1: Recall form methods and their effects on URL

   GET method appends form data as query parameters in the URL, POST does not.

2. Step 2: Connect GET method to Remix loader behavior

   Remix loader reads query parameters from the URL, so GET is required to trigger it with search terms.

3. Final Answer:

   GET -> Option D

4. Quick Check:

   GET method appends query to URL = A [OK]

Hint: Use GET to put search terms in URL for loader to read [OK]

Common Mistakes:

• Using POST which hides query from URL
• Confusing PUT or DELETE with form submission
• Not specifying method defaults to GET but unclear

3. Given this loader code snippet in Remix, what will be the output if the URL is ?q=apple and the data array is ["apple", "banana", "apricot"]?

export async function loader({ request }) {
  const url = new URL(request.url);
  const q = url.searchParams.get('q')?.toLowerCase() || '';
  const data = ["apple", "banana", "apricot"];
  return data.filter(item => item.toLowerCase().includes(q));
}

medium

A. ["apple"]

B. ["banana"]

C. []

D. ["apple", "apricot"]

Solution

1. Step 1: Extract the search query and convert to lowercase

   The query is 'apple', converted to 'apple'.

2. Step 2: Filter data array for items including 'apple'

   "apple" includes 'apple', "apricot" includes 'ap' but not 'apple', but since includes checks substring, only "apple" matches fully, "apricot" does not include 'apple'. Actually, 'apricot' includes 'ap' but not 'apple'. So only "apple" matches.

3. Step 3: Re-examine filtering logic

   Since filter uses includes(q), only items containing 'apple' substring pass. "apple" matches, "apricot" does not contain 'apple'. So output is ["apple"].

4. Final Answer:

   ["apple"] -> Option A

5. Quick Check:

   Filter by 'apple' substring = D [OK]

Hint: Check substring match carefully in filter includes() [OK]

Common Mistakes:

• Assuming 'apricot' contains 'apple'
• Ignoring case conversion
• Returning all items without filtering

4. Identify the error in this Remix loader code for search and how to fix it:

export async function loader({ request }) {
  const url = new URL(request.url);
  const q = url.searchParams.get('query');
  const data = ["cat", "dog", "bird"];
  return data.filter(item => item.includes(q));
}

medium

A. The filter callback should convert both item and q to lowercase for case-insensitive search

B. The loader should return a JSON response using json() helper

C. The search parameter key should be 'q' instead of 'query'

D. The URL object cannot be created from request.url

Solution

1. Step 1: Check the search logic for case sensitivity

   The code gets q without toLowerCase() and filters item.includes(q) without lowering item, making it case-sensitive and prone to errors if q is null.

2. Step 2: Identify need for case-insensitive filtering

   Fix by setting const q = url.searchParams.get('query')?.toLowerCase() || ''; and filter(item => item.toLowerCase().includes(q)).

3. Final Answer:

   The filter callback should convert both item and q to lowercase for case-insensitive search -> Option A

4. Quick Check:

   Case-insensitive search needs toLowerCase on item and q = C [OK]

Hint: Convert item and q to lowercase for case-insensitive search [OK]

Common Mistakes:

• Returning raw arrays instead of json()
• Ignoring case sensitivity in search
• Misnaming query parameter key

5. You want to implement a search in Remix that filters a list of products by name or category using the query parameter q. Which approach correctly handles empty queries and case-insensitive matching in the loader?

export async function loader({ request }) {
  const url = new URL(request.url);
  const q = url.searchParams.get('q')?.toLowerCase() || '';
  const products = [
    { name: 'Table', category: 'Furniture' },
    { name: 'Chair', category: 'Furniture' },
    { name: 'Apple', category: 'Fruit' }
  ];
  // Which filter code is correct?
}

hard

A. return json(products.filter(p => p.name.toLowerCase() === q || p.category.toLowerCase() === q));

B. return json(products.filter(p => p.name.includes(q) || p.category.includes(q)));

C. return json(products.filter(p => p.name.toLowerCase().includes(q) || p.category.toLowerCase().includes(q)));

D. return json(products.filter(p => p.name.toLowerCase().startsWith(q) || p.category.toLowerCase().startsWith(q)));

Solution

1. Step 1: Handle empty query and case-insensitive search

   Using q = ... || '' ensures empty query is handled. Converting both fields and query to lowercase enables case-insensitive matching.

2. Step 2: Choose filter logic for substring matching

   return json(products.filter(p => p.name.toLowerCase().includes(q) || p.category.toLowerCase().includes(q))); uses includes with lowercase conversion on both sides, correctly matching partial substrings in name or category.

3. Final Answer:

   return json(products.filter(p => p.name.toLowerCase().includes(q) || p.category.toLowerCase().includes(q))); -> Option C

4. Quick Check:

   Case-insensitive includes with empty query handled = C [OK]

Hint: Use toLowerCase() and includes() for flexible, case-insensitive search [OK]

Common Mistakes:

• Not converting strings to lowercase
• Using strict equality instead of includes
• Ignoring empty query fallback