Add interpolation of association conditions back in, in the form of proc { ... } rather than instance_eval-ing strings

[#6419 state:committed]
Signed-off-by: NSantiago Pastorino <santiago@wyeworks.com>

Signed-off-by: NSantiago Pastorino <santiago@wyeworks.com>

Signed-off-by: NSantiago Pastorino <santiago@wyeworks.com>

[#6423 state:committed]
Signed-off-by: NSantiago Pastorino <santiago@wyeworks.com>

Applied changes to stylesheet_link_tag from javascript_include_tag which corrects issues with ordering and duplicates.

This corrects two issues with javascript_include_tag, the order at which they are expanded, and removing duplicates.

When individual js assets are specified, they will override the order of the same asset specified in an expansion.

[#5938 state:resolved]

Signed-off-by: NSantiago Pastorino <santiago@wyeworks.com>

As per the HTML 4.01 spec:

  Buttons created with the BUTTON element function just like buttons
  created with the INPUT element, but they offer richer rendering
  possibilities: the BUTTON element may have content. For example, a
  BUTTON element that contains an image functions like and may resemble
  an INPUT element whose type is set to "image", but the BUTTON element
  type allows content.

Since rich content is the main purpose of the <button> element, it makes
sense for the button_tag helper to accept a block.

http://www.w3.org/TR/html401/interact/forms.html#edef-BUTTON
http://dev.w3.org/html5/spec/the-button-element.html#the-button-elementSigned-off-by: NSantiago Pastorino and Emilio Tagua <santiago+emilioe@wyeworks.com>

"submit" is the default value of the <button> element's type attribute
according to the HTML 4.01 and the HTML5 draft specs, so if button_tag
is going to have a default, type="submit" is a more sensible choice than
type="button".

http://www.w3.org/TR/html401/interact/forms.html#adef-type-BUTTON
http://dev.w3.org/html5/spec/the-button-element.html#attr-button-typeSigned-off-by: NSantiago Pastorino and Emilio Tagua <santiago+emilioe@wyeworks.com>

Updated the json date regex to recognize xmlschema formatted date times during json decoding. [#3031 state:resolved]
Signed-off-by: NSantiago Pastorino and Emilio Tagua <santiago+emilioe@wyeworks.com>

Fixes an issue when decoding a json string which looks like a date but is invalid. This DateTime parse error is now caught and the original string is instead passed back [#6286 state:resolved]
Signed-off-by: NSantiago Pastorino <santiago@wyeworks.com>