bee8926d1e
This should fix the deprecation warnings the plugin is throwing with Jekyll 3.0.
```
Deprecation: Document#slug is now a key in the #data hash.
Called by /home/tim/.rvm/gems/ruby-2.2.3/gems/algoliasearch-jekyll-0.5.3/lib/record_extractor.rb:35:in `metadata'.
Deprecation: Document#tags is now a key in the #data hash.
Called by /home/tim/.rvm/gems/ruby-2.2.3/gems/algoliasearch-jekyll-0.5.3/lib/record_extractor.rb:53:in `tags'.
```
I've fighted hard, but we can now launch the tests for both Jekyll 2.5 and Jekyll 3.0 (everything is in `./scripts`), and write tests conditionnaly for one version or the other.
The tool to do that is [appraisal](https://github.com/thoughtbot/appraisal) that lets you define several Gemfiles, and you then have to prefix all your `bundle` commands with `appraisal` (so, yeah, you end up with silly `appraisal bundle exec rake stuff`).
I had to duplicate the fixtures, for each version, which explain the large number of file changed, but this is just a copy paste (except the `_config.yml` that is different for each jekyll version)
245 B
245 B
| title |
|---|
| Hierarchy test |
H1
TEXT1-H1
H2A
TEXT2-H2A-H1
TEXT3-H2A-H1
H2B
TEXT4-H2B-H1
H3A
TEXT5-H3-H2B-H1
H4
TEXT7-H4-H3-H2B-H1
H2C
TEXT8-H2C-H1
H3B <code>
TEXT9-H3B-H2C-H1