You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Large <code> blocks cause an error: "The jekyll-algolia plugin detected that one of your records exceeds the 10.00 Kb record size limit."
What is your expected behavior?
jekyll-algolia should automatically split these blocks into smaller records to avoid exceeding the size limit.
These <code> blocks are coming from Markdown ``` blocks. So there isn't a straightforward way for me to split them up: additional chunks would be visually rendered with separate borders around them. Whereas it seems that jekyll-algolia could do this pretty easily. It doesn't really matter where it chooses to split the code. I just want my search index to be able to find the page that contains that text.
Git repository to reproduce the issue:
Example documentation page with a large code block:
What is the current behavior?
Large
<code>
blocks cause an error: "The jekyll-algolia plugin detected that one of your records exceeds the 10.00 Kb record size limit."What is your expected behavior?
jekyll-algolia should automatically split these blocks into smaller records to avoid exceeding the size limit.
These
<code>
blocks are coming from Markdown```
blocks. So there isn't a straightforward way for me to split them up: additional chunks would be visually rendered with separate borders around them. Whereas it seems that jekyll-algolia could do this pretty easily. It doesn't really matter where it chooses to split the code. I just want my search index to be able to find the page that contains that text.Git repository to reproduce the issue:
Example documentation page with a large code block:
https://rushjs.io/pages/configs/rush_json/
Source code for this page:
https://github.com/Microsoft/rushjs.io-website/edit/master/pages/configs/rush_json.md
Ruby version used:
ruby 2.5.3p105
Jekyll version used:
jekyll 3.7.4
The text was updated successfully, but these errors were encountered: