Add a test for stringified searchParams in merge

[jaulz]

While using the pagination API I see that the searchParams option is a string and thus it fails at this line.

Checklist

• I have read the documentation.
• I have included a pull request description of my changes.
• I have included some tests.
• If it's a new feature, I have included documentation updates.

[szmarczak]

Fixed in 157e02b

[jaulz]

Great, thanks!

[szmarczak]

Actually I'm wrong. e23b7f9 Sorry 😅

[szmarczak]

You just need to revert your commit and git pull origin master --rebase. Then you can start working on the fix :)

[jaulz]

@szmarczak I just pushed another change which 1) handles searchParams that are passed string, undefined or instances of URLSearchParams via defaults and 2) prevents duplications of search params. Though, I'm not sure if the second will cause regressions because it changes the behaviour how searchParams are merged. However, in the context of paging there would be no other way to force setting only one key in the URL as it would result in a URL like this: ?page=1&page=2&page=3&page=4... (not sure if you meant that with your previous comment).

[szmarczak]

I don't think you fixed 1) because as mentioned before it worked even without your changes. You need to provide another test if you think otherwise ;) sorry I was wrong again

[szmarczak]

This PR partially is covered by #1229 Fixed the merge conflict. Thanks! 🙌