refactor the naming within plugin new generator

Having a method called `full?`, which checks on :full and :mountable
is very confusing. I renamed `full?` to `engine?` and created a `full?`
method that only checks the `:full` option
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
Format routes as html on debug page

When someone gets a routing exception, the routes are rendered (starting in Rails 4.0). This PR brings parity between the html routes in the `rails/info/routes` path and when rendered from an exception. This is the continuation of #8521 which brought html formatted routes. 

In addition to bringing parity to the two views, we're keeping our views DRY by rendering off of the same partials. In this case Railties depends on partials provided by ActionDispatch. I'm open to alternative implementations. Ideally both views will use the same code so any improvements or updates to it will be reproduced on both.

<hr />

![](http://f.cl.ly/items/3O1D0K1v0j0i343O3T3T/Screen%20Shot%202012-12-17%20at%203.07.20%20PM.png)
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]
Merge pull request #8543 from schneems/schneems/html-route-error

Format routes as html on debug page
handle protocol option in stylesheet_link_tag and javascript_include_tag

closes #8388
Merge pull request #8389 from nashby/issue-8388

handle protocol option in stylesheet_link_tag and javascript_include_tag
Minor js review [ci skip]

Remove/add ; where necessary, fix indentation.
Added support for validates_uniqueness_of in PostgreSQL array columns. Fixes: #8075.
Refactor uniqueness validator logic a bit

Cleanup some code, avoid extra hash with reverse_merge, and don't use
send for :id, since it's always present.
Remove prepend_and_append requirement from AS

It's not necessary to use this extension here, we are fine with Array#unshift.
Avoid unnecessary hashes with error options
Simplify value logic by always typecasting
Change relation in place
Extract some methods
Merge branch 'uniqueness-validation-postgresql-arrays'

When setting an array column (or other PostgreSQL-specific data type)
to be validated for uniqueness, the resulting SQL query is generated with
syntax errors, like this:

    SELECT 1 AS one FROM "postgresql_arrays"
    WHERE "postgresql_arrays"."nicknames" = '["john", "johnny"]' LIMIT 1

This happens because Ruby Arrays must be type-casted to their PostgreSQL
equivalent. This small patch fixes this issue, calling the adapter's
type_cast method.

Closes #8077
Add app/models/concerns and app/controllers/concerns to the default directory structure and load path
Merge
Fix changelog