fix(Search, Typescript): Allow creating GSearchRequest without 'q' (but requiring 'filters')

[jbottigliero]

https://docs.globus.org/api/search/reference/post_query/#gsearchrequest

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.79%. Comparing base (52863ec) to head (c4521cb).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #777   +/-   ##
=======================================
  Coverage   95.79%   95.79%           
=======================================
  Files          86       86           
  Lines        1759     1759           
  Branches      294      294           
=======================================
  Hits         1685     1685           
  Misses         73       73           
  Partials        1        1           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[jakeglobus]

I don't understand what this is supposed to be testing. When is requireOneFilter expected to be undefined? Is this to produce a typescript error if GSearchRequest is changed in a way that's incompatible with having an empty filters array?

[jbottigliero]

Yes, this is only a Typescript assertion, the // @ts-expect-error is ensuring that filters: [] is not acceptable.

The expect(requireOneFilter).toBeDefined() is to avoid the unused variable error.

[jakeglobus]

Ohhhh, I see now, thanks!