1
0
Fork 0
mirror of https://github.com/activerecord-hackery/ransack.git synced 2022-11-09 13:47:45 -05:00

[skip ci] Update docs for 1.6.5 release

This commit is contained in:
Jon Atack 2015-03-28 15:55:18 +05:30
parent b2e55d8853
commit d9d211ee51
2 changed files with 39 additions and 40 deletions

View file

@ -1,32 +1,47 @@
# Change Log
## Unreleased
## Version 1.6.5 - 2015-03-28 - Rails 5.0.0 update
### Added
* [WIP/experimental] Add compatibility with Rails 5/master and Arel 7.
* Update the Contributing Guide with detailed steps for contributing to
Ransack.
* Broaden the test suite database options in `schema.rb` and add
code documentation.
* Improve the header message when running tests.
*Jon Atack*
* Allow `:wants_array` to be set to `false` in the predicate options
([#32](https://github.com/activerecord-hackery/ransack/issues/32)).
*Michael Pavling*
* Add a failing spec for issue
[#374](https://github.com/activerecord-hackery/ransack/issues/374).
*Jamie Davidson*
*Jamie Davidson*, *Jon Atack*
* Allow `:wants_array` to be set to `false` in the predicate options.
([#32](https://github.com/activerecord-hackery/ransack/issues/32))
*Michael Pavling*
* Clarify database options and improve the header message when running tests.
*Jon Atack*
* [WIP/experimental] Fix compatibility with Rails 5/master and Arel 7.
*Jon Atack*
### Fixed
* Stop relying on Active Record::relation#where_values which are deprecated
in Rails 5.
* Make the ransacker_args test work correctly with Sqlite3.
*Jon Atack*
### Changed
* Stop CI testing for Rails 3.0 to reduce the size of the Travis test matrix.
*Jon Atack*
## Version 1.6.4 - 2015-03-20
## Version 1.6.4 - 2015-03-20 - Rails 4.2.1 update
* ActionView patch to maintain compatibility with Rails 4.2.1 released today.
@ -42,6 +57,7 @@
*Denis Tataurov*, *Jon Atack*
## Version 1.6.3 - 2015-01-21
* Fix a regression
@ -173,24 +189,22 @@
## Version 1.5.1 - 2014-10-30
### Fixed
* Fix a regression caused by incorrect string constants in `context.rb`.
*Kazuhiro Nishiyama*
### Added
* Add base specs for search on fields with `_start` and `_end`.
*Jon Atack*
* Add a failing spec for detecting attribute fields containing `_and_` that
needs to be fixed. Attribute names containing `_and_` and `_or_` are still
not parsed/detected correctly.
*Jon Atack*
### Fixed
* Fix a regression caused by incorrect string constants in `context.rb`.
*Kazuhiro Nishiyama*
### Changed
* Remove duplicate code in `spec/support/schema.rb`.
@ -267,7 +281,6 @@
## Version 1.4.1 - 2014-09-23
### Fixed
* Fix README markdown so RubyGems documentation picks up the formatting correctly.

View file

@ -27,8 +27,8 @@ instead.
If you're viewing this at
[github.com/activerecord-hackery/ransack](https://github.com/activerecord-hackery/ransack),
you're reading the documentation for the master branch with the latest features.
[View documentation for the last release (1.6.4).]
(https://github.com/activerecord-hackery/ransack/tree/v1.6.4)
[View documentation for the last release (1.6.5).]
(https://github.com/activerecord-hackery/ransack/tree/v1.6.5)
## Getting started
@ -56,20 +56,6 @@ Or, if you would like to use the latest updates, use the `master` branch:
gem 'ransack', github: 'activerecord-hackery/ransack'
```
The other branches (`rails-4`, `rails-4.1`, and `rails-4.2`) were each used for
developing and running Ransack with the latest upcoming version of Rails at the
time. They are smaller and possibly slightly faster because they do not have to
support previous versions of Rails and Active Record. Once support for that
Rails version is merged from the branch into Ransack master, the branch is no
longer actively maintained -- unless the open source community submits pull
requests to maintain them. You are welcome to do so!
To use one of the branches, for example the `rails-4.1` branch:
```ruby
gem 'ransack', github: 'activerecord-hackery/ransack', branch: 'rails-4.1'
```
## Usage
Ransack can be used in one of two modes, simple or advanced.