README.md in array_include_methods-1.0.2 vs README.md in array_include_methods-1.0.3

- old
+ new

@@ -1,18 +1,20 @@ -# ArrayIncludeMethods 1.0.2 - Ruby Refinement +# ArrayIncludeMethods 1.0.3 - Ruby Refinement [![Gem Version](https://badge.fury.io/rb/array_include_methods.svg)](http://badge.fury.io/rb/array_include_methods) +[![Build Status](https://travis-ci.com/AndyObtiva/array_include_methods.svg?branch=master)](https://travis-ci.com/AndyObtiva/array_include_methods) +[![Coverage Status](https://coveralls.io/repos/github/AndyObtiva/array_include_methods/badge.svg?branch=master)](https://coveralls.io/github/AndyObtiva/array_include_methods?branch=master) `Array#include_all?` & `Array#include_any?` methods missing from basic Ruby `Array` API. ## Setup ### With Bundler: Include the following in Gemfile: ```ruby -gem 'array_include_methods', '~> 1.0.2' +gem 'array_include_methods', '~> 1.0.3' ``` Run: ``` @@ -22,11 +24,11 @@ ### Without Bundler: Run: ``` -gem install array_include_methods -v1.0.2 +gem install array_include_methods -v1.0.3 ``` ## Usage Add the following line to your application if you are not requiring all gems via Bundler (e.g. `Bundler.require(:default)`): @@ -61,22 +63,20 @@ [1, 2, 3, 4].include_any?([6, 7]) # returns false [1, 2, 3, 4].include_any?([]) # returns true [1, 2, 3, 4].include_any?(nil) # returns false ``` -## Change Log +## Opal Compatibility -### 1.0.2 +This gem degrades gracefully to monkey-patching in Opal Ruby and provides a `using` method shim so consumer code does not have to change if it used gems that rely on the Ruby refinement -- Handled case of two arrays with elements of unsortable object types (e.g. Hash) +## TODO -### 1.0.1 +[TODO.md](TODO.md) -- Handled case of two arrays with different ordering of common elements +## Change Log -### 1.0.0 - -- Initial implementation of Array#include_all? & Array#include_any? +[CHANGELOG.md](CHANGELOG.md) ## Contributing to array_include_methods * Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet. * Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it.