Tags: algolia/jekyll-algolia
Tags
release 1.7.0 feat: Expose --future and --drafts options (#173) docs: add GitHub Actions to pages documentation fixes #165 Co-Authored-By: dieghernan@users.noreply.github.com docs: add note about maintenance status (#153) * Update getting-started.md * Update README.md * Apply suggestions from code review Co-authored-by: Sarah Dayan <sarah.dayan@algolia.com> Co-authored-by: Sarah Dayan <sarah.dayan@algolia.com> Updating documentation website
release 1.6.0 chore: fix lint feat(settings): allow disabling overriding (#118) * feat(settings): allow disabling overriding * test(settings): add new _fancy_ tests * docs(settings): document false behaviour * test: five normal thingie * fix(tests): correct default value * test: try thawing the value * fix: don't use default value unless 'nil' I don't see how to test this * Update options.md * Update configurator.rb * Update indexer.rb * update tests * Update configurator_spec.rb * test me travis? * Update lib/jekyll/algolia/indexer.rb
release 1.4.8 This release fixes a bug with the jekyll-redirect-from plugin. When using the `redirect_from` option it provides, `jekyll-algolia` was trying to index non-existing files and throwing errors. We now exclude any file that has its layout set to `redirect`. It solves potentially wider issues than just `jekyll-redirect-from`, because we assume that a layout called `redirect` means that the page is only here for redirection and doesn't need to be index. We also disable the `autopage` feature of `jekyll-paginate-v2` as it is also creating new pages that don't contain any content worth indexing.
release 1.4.7 This release fixes an edge-case where collection item dates where not correctly converted to Date objects and kept as String when passed to the plugin. The inside conversion to timestamp would fail and break the indexing. This release now checks if dates are actually string, and try to gracefully convert them to date object before converting, if such a conversion is possible.
release 1.4.6 The release fixes the way record size is calculated. It used to naively just take the length of the JSON but it now correctly uses the bytesize (taking UTF-8 characters into account). This fix will now correctly warn about records slightly above the limit that used to go through before.
PreviousNext