yujonglee

Add client-side rate-limiter

1

- [ ] Using fixed-window, in-memory. - [ ] Using [reCAPCHA](https://developers.google.com/recaptcha/intro).

We first experienced this with Litellm docs, and I thought it was fixed after switching from our custom debounce logic to pagefind's `debouncedSearch` api. (https://pagefind.app/docs/api/#debounced-search) But it seems like it...

https://github.com/fastrepl/canary/blob/9babc5414234722ef716add1807ec171480e9af5/js/packages/web/src/canary-search-results-group.ts#L42-L44 This should not needed. But while doing https://github.com/fastrepl/canary/commit/9babc5414234722ef716add1807ec171480e9af5, `this.groups` is string, not array on render. This is just a workaround for now.

import from `@generated/pagefind/pagefind` in `@getcanary/docusaurus-pagefind`

1

```diff export default function plugin(_context, options) { const { indexOnly = false } = options; let generatedPath = null; const config = { name: "docusaurus-plugin-pagefind-canary", async contentLoaded({ actions }) {...

Reference: https://typesense.org/docs/

can be used for debounce, CAPTCHA, etc

Ideally, provider should be able to nested, and outer provider should work as a fallback.

OpenAPI support

2

https://github.com/aj-foster/open-api-generator/blob/main/lib/open_api/spec.ex Also, we should modify our crawler to not chunk OpenAPI spec.