update csv docs to use GFM
Allow customized text for new record link in has_many forms.

Overload the :new_record option, so that if a string is provided, it
will use the string for the new_record link text. Fallback to the
existing behavior if :new_record is not a string.
Merge pull request #2636 from clalimarmo/custom-has-many-new-record-link

Allow customized text for new record link in has_many forms.
has_many form code style update
remove old form code
add an overall description to the AA form builder
update the way has_many form fields are built

If a user clicks the create button in rapid succession, it's possible
for you to have multiple new records with the same identifier. This
change adopts the same identifying scheme that the form itself already
uses for child records: a numeric index.
update 5-forms.md to use GFM :bowtie:
bump Travis to use the latest Rails versions
Version bump to 1.0.0.pre
Merge pull request #2640 from shekibobo/100-pre

Bump master to 1.0.0.pre
Improve comments_spec styles and readability
Make resource_type of AA::Comment respect STI
Convert tabs to spaces
reorganize javascript folder structure
Fix overlapping flash message on non-logged pages

Add some margin-bottom to flash messages on logged out pages
Merge pull request #2651 from brennovich/2650-overlapping-flash-messages-on-login

Fix overlapping flash message on non-logged pages
has_many javascript refactor

First and foremost, this commit moves the JS `onclick` calls out into
their own dedicated file. This also adds before & after hooks so you
can more easily update dynamic parts of the form, for example if you're
using a plugin like Chosen for interactive dropdowns:

```coffee
$ ->
  $(document).on 'has_many_add:after', '.has_many', (e, fieldset)->
    fieldset.find('select').chosen()
```

There's one other change here: I switched around the text used for
has_many deletion because it didn't make sense to me that delete was
applied to something that hadn't yet been saved, while remove was used
for already-saved records.
Merge pull request #2645 from seanlinsley/refactor/has_many-form

Refactor the has_many form
Allow datepicker options to be passed to datepicker_input

Allows :max_date and :min_date options (or other jQueryUI datepicker
options) to be passed to :datepicker input.

```ruby
f.input :starts_at, as: :datepicker, datepicker_options: {min_date:
"2013-10-8", max_date: 3.days.from_now.to_date}
f.input :ends_at, as: :datepicker, datepicker_options: {min_date:
3.days.ago.to_date, max_date: "+1W +5D"}
```