Unset route query on default value is not working anymore

[greenhalos]

Describe the bug

Setup

Package: @vueuse/router

<script setup>
import { useRouteQuery } from "@vueuse/router";
const search = useRouteQuery("search", "defaultValue");
</script>

Expected Beahviour and Behaviour of Version v10.2.1

When I change the value of search to the default value (in this case "defaultValue"), the query parameter is removed from the URL:

search.value = "defaultValue";

Behaviour in Version v10.3.0

When changing the value of search to the default value (in this case "defaultValue"), the parameter remains in the URL.

Further Notes

In my production use case the default value is "" which leads to to a paramter ?search=

Further observations

• It was intended behaviour in the past, as far as I can tell: fix(useRouteQuery): unset route query on default value #1490
• It was remove in 0d02f6c as part of fix(router): improves router functions: synchronize values, adds tests, and optimize performance #3184
• There is one Discussion about the same method, but is more about a changed behaviour Differentiate undefined and null in useRouteQuery #2914

Reproduction

https://github.com/greenhalos/useRouteQuery-bug-default

System Info

Binaries:
    Node: 18.15.0 - ~/.nvm/versions/node/v18.15.0/bin/node
    npm: 9.5.0 - ~/.nvm/versions/node/v18.15.0/bin/npm
    pnpm: 8.6.11 - ~/.local/share/pnpm/pnpm
  npmPackages:
    @vueuse/core: 10.3.0 => 10.3.0 
    @vueuse/router: 10.3.0 => 10.3.0 
    vue: ^3.2.25 => 3.3.4

Used Package Manager

npm

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a VueUse issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/core instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion.
• The provided reproduction is a minimal reproducible example of the bug.

[vuthanhbayit]

I just want to ask, when I use:

const state = reactive({
  name: useRouteQuery('name', ''),
})

watch(state, (newValue, oldValue) => {
  console.log(newValue === oldValue) // true
  console.log(newValue.name === oldValue.name) // true
})

when changing the value of state.name, console.log in watch returns true.
How does it work? Tks for watching

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[greenhalos]

I have rebased the pull request to the latest commits of the main branch, so it is ready again to be reviewed

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[greenhalos]

It is fixed via #3583