Remove unnecessary require in ImageHelper.
Remove duplicate validity spec and stub out config values instead of setting them directly.
Only allow to update image if the image being uploaded has the same file name as the image being replaced.
Allow original thumbnail to be shown when a file name validation fails.
Fix issue where form was squashed when image thumbnail was short.
Added 'placeholder' attribute to the 'input' tag

Fix for https://github.com/resolve/refinerycms/issues/1870

Made following changes to the validation section of the `input` tag:
  - Added the missing `placeholder` attribute.
  - Removed `placeholder` as one of the possible values for the `type` tag.  Refer to the spec(http://www.w3.org/TR/html5/the-input-element.html#attr-input-type) for more details.
Merge pull request #1871 from kandadaboggu/patch-2

Added 'placeholder' attribute to the 'input' tag
Fix typo
Merge pull request #1876 from Aupajo/patch-1

Fix typo
Tiny changes to sk files
Add failing spec for #1585.
Fix reordering shuffle that causes 11th+ items to be moved upward in chain.
Lock to sass 3.1.12 so that tests pass.

They fail on 3.2.0 because of nex3/sass#482
Adds entry respecting #1882 to changelog.
Revert "Lock to sass 3.1.12 so that tests pass."

This reverts commit 6672d9edcfbb9a300b21c76c4f0435bd3e48f799.
Sass 3.2.1 is out and fixes the issue.
Make multiple resource uploads pass on form parameters, which should be expected behaviour.

In the situation where you add a field to Resources, upon create, you're unable to save any of those additional attributes because we only pass on the file attribute at the moment when the user is uploading multiple files. Of course, the user is always uploading multiple files, because the default html5ish behaviour is to send an array anyway. This corrects the existing create method and allows the user to submit multiple attributes to be saved.
Merge pull request #1884 from resolve/resource-accept-params

Make multiple resource uploads pass on form parameters, which should be ...
Added spec for testing that migration for a new resource in an extension will be numbered properly as reported in GH-1885
Fixing the regex used for detecting that a generator template was a migration (it didn't include final '.erb'). Related to the issue GH-1885 about bad revisions numbering
Added spec to test that routes for the new resource are appended to the config/routes.rb file as reported in GH-1885