Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

@algolia autocomplete-shared throws a warning regarding 'render' option #148

Closed
jkohlin opened this issue Oct 5, 2022 · 0 comments · May be fixed by mdomorffaruk/dispatch#4 or tahabiyikli/dispatch1#2
Labels
bug Something isn't working

Comments

@jkohlin
Copy link

jkohlin commented Oct 5, 2022

Please describe the bug you are seeing

I get this warning when adding the plugin in docusaurus v2.1.0

[Autocomplete] You provided the 'render' option but did not provide a 'renderer.render'. Since v1.6.0, you can provide a 'render' function directly in 'renderer'.
To get rid of this warning, do any of the following depending on your use case.
- If you are using the 'render' option only to override Autocomplete's default 'render' function, pass the 'render' function into 'renderer' and remove the 'render' option.
- If you are using the 'render' option to customize the layout, pass your 'render' function into 'renderer' and use it from the provided parameters of the 'render' option.
- If you are using the 'render' option to work with React 18, pass an empty 'render' function into 'renderer'.
See https://www.algolia.com/doc/ui-libraries/autocomplete/api-reference/autocomplete-js/autocomplete/#param-render

How can we best reproduce the bug?

go to https://codesandbox.io/s/gallant-sara-ietpq9?file=/package.json

Which version of Docusaurus and @cmfcmf/docusaurus-search-local are you using?

moderskeppet-docs@0.0.0 /Users/xxxx/xxxx/docusaurus/moderskeppet-docs
├─┬ @cmfcmf/docusaurus-search-local@0.11.0
│ └── @docusaurus/core@2.1.0 deduped
├── @docusaurus/core@2.1.0
└─┬ @docusaurus/preset-classic@2.1.0
├── @docusaurus/core@2.1.0 deduped
├─┬ @docusaurus/plugin-content-blog@2.1.0
│ └── @docusaurus/core@2.1.0 deduped
├─┬ @docusaurus/plugin-content-docs@2.1.0
│ └── @docusaurus/core@2.1.0 deduped
├─┬ @docusaurus/plugin-content-pages@2.1.0
│ └── @docusaurus/core@2.1.0 deduped
├─┬ @docusaurus/plugin-debug@2.1.0
│ └── @docusaurus/core@2.1.0 deduped
├─┬ @docusaurus/plugin-google-analytics@2.1.0
│ └── @docusaurus/core@2.1.0 deduped
├─┬ @docusaurus/plugin-google-gtag@2.1.0
│ └── @docusaurus/core@2.1.0 deduped
├─┬ @docusaurus/plugin-sitemap@2.1.0
│ └── @docusaurus/core@2.1.0 deduped
├─┬ @docusaurus/theme-classic@2.1.0
│ └── @docusaurus/core@2.1.0 deduped
└─┬ @docusaurus/theme-search-algolia@2.1.0
└── @docusaurus/core@2.1.0 deduped

Which Node.js version are you using?

v16.14.0

Which theme are you using?

Yes, I am using @docusaurus/theme-classic

How does your plugin config look like?

    [
      require.resolve("@cmfcmf/docusaurus-search-local"),
      {
        language: "sv",
        indexPages: true,
      },
    ],

Additional context

Also reported as a bug to facebook/docusaurus#8178

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
1 participant