🚨 IMPORTANT: Please do not create a Pull Request without creating an issue first.

Any change needs to be discussed before proceeding. Failure to do so may result in the rejection of
the pull request.

Description

Client - Deep objects are sent as empty string in query parameters.
This makes the client unsuitable for use with JSON:API sparse fieldsets

Related #516

Type of change

Please delete options that are not relevant.

• Breaking change (fix or feature that would cause existing functionality to not work as
  expected)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can
reproduce. Please also list any relevant details for your test configuration

• yarn test packages/fets/tests/client-query-serialization.spec.ts

Running the test will perform a query to https://postman-echo.com/ to assert that the request sent by the client contains the expected query parameters.

Test Environment:

• OS: macOS
• package-name: fets
• NodeJS: no

Checklist:

• I have followed the
  CONTRIBUTING doc and the
  style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
  -> No changeset generated yet
• My changes generate no new warnings
  -> GitHub Codespaces shows a linting error in my test file, I don't now why
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests and linter rules pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
  -> I am not aware of any downstream module which would be affected by this

Further comments

This change, albeit small, is a breaking change: people who would expect objects to be stripped from the query parameters sent by the client will now see them sent to the server. I won't probably cause any issue, but…