Search implementation in Remix - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the hook used for reading URL search parameters in Remix.

Remix

import { [1] } from "@remix-run/react";

Drag options to blanks, or click blank then click option'

AuseActionData

BuseNavigate

CuseLoaderData

DuseSearchParams

Attempts:

3 left

💡 Hint

Common Mistakes

Importing useLoaderData instead, which is for loader data, not URL params.

Using useNavigate which is for navigation, not reading search params.

The useSearchParams hook lets you read and update the URL's query string in Remix.

2fill in blank

medium

Complete the code to get the current search query from the URL parameters.

Remix

const [searchParams] = [1]();
const query = searchParams.get("q") || "";

Drag options to blanks, or click blank then click option'

AuseSearchParams

BuseActionData

CuseLoaderData

DuseNavigate

Attempts:

3 left

💡 Hint

Common Mistakes

Trying to get searchParams from useLoaderData which does not provide URL params.

Using useNavigate which is for navigation, not reading params.

useSearchParams returns an array where the first element is the current URL search parameters object.

3fill in blank

hard

Fix the error in the loader function to read the search query from the request URL.

Remix

export async function loader({ request }) {
  const url = new URL(request.[1]);
  const q = url.searchParams.get("q") || "";
  return { q };
}

Drag options to blanks, or click blank then click option'

Amethod

Bbody

Curl

Dheaders

Attempts:

3 left

💡 Hint

Common Mistakes

Using request.body which is a stream, not a URL string.

Using request.method which is the HTTP method, not the URL.

The request.url property contains the full URL string, which you can pass to the URL constructor to access search parameters.

4fill in blank

hard

Fill both blanks to create a form that submits the search query using GET method and updates the URL.

Remix

<form method=[1] action="/search">
  <input type="search" name=[2] aria-label="Search query" />
  <button type="submit">Search</button>
</form>

Drag options to blanks, or click blank then click option'

A"get"

B"post"

C"q"

D"query"

Attempts:

3 left

💡 Hint

Common Mistakes

Using POST method which sends data in the body, not URL.

Using a different input name that doesn't match the query parameter.

Using method="get" makes the form submit the query in the URL. The input's name must match the query parameter key, here "q".

5fill in blank

hard

Fill all three blanks to display the search query from loader data and update the input value accordingly.

Remix

export default function SearchPage() {
  const data = useLoaderData();
  return (
    <main>
      <form method="get">
        <input
          type="search"
          name="q"
          aria-label="Search query"
          defaultValue=[1]
        />
        <button type="submit">Search</button>
      </form>
      <p>Showing results for: <strong>[2]</strong></p>
      <ul>
        {data.results?.map((item) => (
          <li key={item.id}>{item.[3]</li>
        ))}
      </ul>
    </main>
  );
}

Drag options to blanks, or click blank then click option'

Adata.q

Ctitle

Dname

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'value' instead of 'defaultValue' which makes the input controlled without onChange.

Displaying the wrong property from items, like 'name' instead of 'title'.

The input's defaultValue and the displayed query text both come from data.q. The list shows each item's title property.

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