NuxtN
Nuxt•2y ago
Fabian B.

Reactive Route Search Query Composable

Does somebody have deeper experience with this?

I am trying to implement a composable to reactively use a route search query. Meaning that the value updates reactively whenever the route query parameter changes. And when setting a new value with .value, it does a navigateTo() in the background.

However, there are issues with SSR, which makes it hard to implement this. This is how I got so far:

export const useRouteSearchQuery = ({
  name = "q",
  defaultValue = "",
  replace = false,
}: { name?: string; defaultValue?: string; replace?: boolean } = {}) => {
  const requestUrl = useRequestURL();
  const route = useRoute();

  const searchQuery = computed({
    get: () => {
      console.log("-> getter", {
        routeVal: route.query[name],
        staticVal: requestUrl.searchParams.get(name),
      });

      // Reactive, but doesnt work in ssr
      const routeVal = route.query[name];
      if (routeVal) return String(routeVal);

      // Non reactive, works in ssr
      const staticVal = requestUrl.searchParams.get(name);
      if (staticVal) return String(staticVal);

      return defaultValue;
    },
    set: (newVal: string | undefined) => {
      const query = { ...route.query };
      if (newVal?.length) {
        query[name] = newVal;
      } else {
        delete query[name];
      }

      navigateTo({ query }, { replace });
    },
  });

  return { searchQuery };
};


Works in most cases, but in the case where I do a navigateTo() in any component (or the user is navigating back & forth) where certain query parameters are getting removed (e.g. from ?foo=bar&xyz=abc to ?foo=bar), it's still not reactive (watching the searchQuery value reacts to changes in the query parameters, not not when it gets removed e.g. from the user navigating back & forth).
Was this page helpful?