Separate functions for createResource with a signal as source vs with a non-signal value

[Gregoor]

I just helped a friend debug an issue with his first foray into Solid. The root of the issue was that he passed a non-signal value into createResource which lead to it not being reactive. The solution was wrapping it in a function. This seems like an easy enough mistake to make (and thus timesink) that we were wondering why there is not a separate function for non-signal values e.g. createStaticResource?

The mistake is so easy to make, that it even made its way into the official docs [here] (and here is the PR to fix it):(https://docs.solidjs.com/guides/routing-and-navigation#accessing-parameters):

import { createResource } from "solid-js";
import { useParams } from "@solidjs/router";

async function fetchUser(id) {
  const response = await fetch(
    `https://jsonplaceholder.typicode.com/users/${id}`
  );
  return response.json();
}

const User = () => {
  const params = useParams();
  const [data] = createResource(params.id, fetchUser); // Pass the id parameter to createResource

  return (
    <div>
      <Show when={!data.loading} fallback={<p>Loading...</p>}>
        <div>
          <p>Name: {data().name}</p>
          <p>Email: {data().email}</p>
          <p>Phone: {data().phone}</p>
        </div>
      </Show>
    </div>
  );
};