feat(search-algolia): algolia externalUrl regex to navigate with window.href

[semoal]

Motivation

Will close #5631, now will be possible to use Algolia native SearchBar with multiple domains on the same Algolia config.

Have you read the Contributing Guidelines on pull requests?

Yes

Test Plan

• Just add to docusaurus.config.js:

 algolia: {
        appId: 'X1Z85QJPUV',
        apiKey: 'bf7211c161e8205da2f933a02534105a',
        indexName: 'docusaurus-2',
        contextualSearch: true,
        externalUrlRegex: 'docusaurus.io'
      },

And immediately after, link hrefs will be converted to absolute and will navigate with window.location instead of history.push

Related PRs

(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/facebook/docusaurus, and link to your PR here.)

[netlify]

✔️ [V2]
Built without sensitive environment variables

🔨 Explore the source changes: ac03ee2

🔍 Inspect the deploy log: https://app.netlify.com/sites/docusaurus-2/deploys/617c2ad000377700086e9e9a

😎 Browse the preview: https://deploy-preview-5795--docusaurus-2.netlify.app

[github-actions]

⚡️ Lighthouse report for the changes in this PR:

Category	Score
🟢 Performance	91
🟢 Accessibility	98
🟢 Best practices	100
🟢 SEO	100
🟢 PWA	95

Lighthouse ran on https://deploy-preview-5795--docusaurus-2.netlify.app/

[slorber]

LGTM, just not a fan of withRegex

[Josh-Cena]

I suggest moving this to jsUtils. We shouldn't keep on adding more files, especially for these general-purpose utilities

[semoal]

imho, it's easier to keep it separated on files for an easier search on the editor. (At least for me)
But as @slorber considers :)

[Josh-Cena]

That really depends on the editor:D Most decent editors allow you to search globally, but navigating in one file is always easier than in a giant directory. If there are more regex tools to come that we can envision, keeping it seperated can be a good idea, but... I'm not sure if there are many painpoints with regex that need utility functions

[slorber]

I don't care too much about the filename as long as the import name is understandable: it's an implementation detail that we can easily refactor later.

Not a fan of a fn with signature RegExp | {test: () => boolean}, what about returning the boolean and calling test() inside directly?

And "" should not be handled like undefined

[semoal]

Yep that makes snse to me too, refactored to be much cleaner.

[slorber]

I would have used a simpler isRegexpStringMatch(regex,str) rather than a higher order function, but it's not too important

[slorber]

I don't care too much about the filename as long as the import name is understandable: it's an implementation detail that we can easily refactor later.

Not a fan of a fn with signature RegExp | {test: () => boolean}, what about returning the boolean and calling test() inside directly?

And "" should not be handled like undefined

[slorber]

hasn't this been reverted? 😅

[semoal]

Damn, force-pushed with --ammend from another computer and forgot to pull.. doing 30 things at the same time isn't good. Should be fixed now

[slorber]

:D LGTM