1
100%
master: 100%

Ran 07 Jan 2016 12:34AM UTC

Files 4

Run time 0s

Badge

Embed ▾

Committed 07 Jan 2016 12:33AM UTC coverage: 99.552%. First build

Job # 2.2, gemfiles/jekyll_v2.gemfile

Build Type

Pull #19

travis-ci

Committed by

pixelastic

Commit Message

fix(v3): Stop throwing deprecation warning when using Jekyll v3

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)

Pull Request Pull Request #19: fix(v3): Stop throwing deprecation warning when using Jekyll v3

Coverage Stats

222 of 223 relevant lines covered (99.55%)

24.88 hits per line

algolia / algoliasearch-jekyll / 78 / 1
100%
master: 100%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 78.1 (2.2, gemfiles/jekyll_v2.gemfile)

algolia / algoliasearch-jekyll / 78 / 1 100% master: 100%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 78.1 (2.2, gemfiles/jekyll_v2.gemfile)

algolia / algoliasearch-jekyll / 78 / 1
100%
master: 100%

README BADGES
x