Refactoring the token_and_options method to fix bugs

Adding a test for the equal trun bug

Adding a test for the after equal trunc bug

Adding a test for the slash bug

Adding a test for the slash quote bug

Adding a helper method for creating a sample request object with token

Writing a method to create params array from raw params

Writing a method to rewrite param values in the params

Writing a method to get the token params from an authorization value

Refactoring the token_and_options method to fix bugs

Removing unnessecary test

A constant for this shared regex seemed appropriate

Wanting to split up this logic

Adding small documentation pieces
Add script_name option description and example for #url_for options
Explain controller specific assets more thoroughly

The current section on controller specific assets does not really explain how the default application.css and application.js files
generated by rails will work with controller specific assets and is a bit ambiguous. We should remind users that they will be included
into their application by default but that they have the option to include them only where needed if they want and how this works with
precompiling assets.

[ci_skip]
Fix: documentation for String#humanize
change spy of  after invoked controller action. because ruby-2.0.0 waned unused variables
Remove Reference to Ruby 1.8.7
Prevent callback from being set twice.

When you add one callack in two separate `set_callback` calls - it is
only called once.

When you do it in one `set_callback` call - it is called twice.

This violates the principle of least astonishment for me. Duplicating
callback is usually an error. There is a correct and obvious way to do
anything without this "feature".

If you want to do

    before_save :clear_balance, :calculate_tax, :clear_balance

or whatever, you should better do

    before_save :carefully_calculate_tax

    def carefully_calculate_tax
      clear_balance
      calculate_tax
      clear_balance
    end

And this even opens gates for some advanced refactorings, unlike the
first approach.

My assumptions are:

- Principle of least astonishment is violated, when callbacks are either
  prevented from duplication, or not.
- Duplicating callbacks is usually an error. When it is intentional -
  it's a smell of a bad design and can be approached without abusing
  this "feature".

My suggestion is: do not allow duplicating callbacks in one callback
call, like it is not allowed in separate callbacks call.
Fix documentation style
Fix CHANGELOG entry about scope change

I missed attribution on this :flushed:
Fix incorrect adjustment 4c41e87e3ae548c44810b66437b2f0f6e73b2106
update AD::Journey to follow Rails coding conventions
Merge pull request #8567 from frodsan/update_coding_conventions_journey

update AD::Journey to follow Rails coding conventions
Merge pull request #8560 from u16suzu/master

Fix document for String#humanize

Conflicts:
	activesupport/lib/active_support/core_ext/string/inflections.rb
Fix indentation issuing warning
Fix doc pointing to non existent logger class [ci skip]
Wrap table creation in a transaction.

This will make the tests pass when the intrange datatype is not present
Revert "Fix incorrect adjustment 4c41e87e3ae548c44810b66437b2f0f6e73b2106"

This reverts commit e1f8ec59f2cc83f052b15233147aa2d6d8114a4d.

Reason: seems bad styling

[ci skip]
copy edits in assets guide [ci skip]
Serialized attribute can be serialized in an integer column

Fix #8575
Merge branch 'master' of github.com:lifo/docrails