clearOnDefault in custom parser

[fazlulShanto]

what wrong i am doing here. i want to show default value in the url. when i change value it does get reflected but not on defualt value.

https://stackblitz.com/edit/vitejs-vite-dgxziane?file=src%2FApp.tsx

[franky47]

Likely this:

eq(dateA, dateB) {
  return false; // Force serialization to ensure consistent formatting and boundary application
},

The point of the eq function, for non-primitive types (like Date here), is to be able to check the value you set against the default value. By returning false, it can never detect this and therefore never clears it from the URL.

[fazlulShanto]

@franky47 what about the other simple one. it was straight forward:

const [randomValues] = useQueryStates({
    foo: parseAsString
      .withDefault('foo-value')
      .withOptions({ clearOnDefault: false }),
    bar: parseAsString
      .withDefault('bar-value')
      .withOptions({ clearOnDefault: false }),
  });

it can never detect this and therefore never clears it from the URL

i actually want it to be shown in the url always, changed/default doesn't matter. but it doesn't show in url at all until i change. i know i can use useEffect but that comes with another cost as i have to fire an api call on dateRange change.

[franky47]

I see, I misunderstood your initial message. clearOnDefault: false works for writes, but indeed there is no mechanism (yet) for writing defaults to the URL automatically (eg: on mount).

There are discussions about this (will add links later), but they'll all be based on useEffect. It shouldn't be a problem as the state value would be the same before and after the sync effect runs anyway, but your API call effect should be able to handle non-primitive data types (eg: two Date objects with different references that resolve to the same point in time).

[fazlulShanto]

thanks for answers 🥂