Skip to content
Commits on Jul 13, 2010
  1. @yabawock
  2. @yabawock
Commits on Jul 12, 2010
  1. @yabawock

    More intelligent way to html_escape labels and hints (GH-299)

    yabawock committed
    This commit won't escape html entities in strings marked as html_safe according to newer rails versions.
    Additionally you can now turn html escaping off by setting
    
    Formtastic::SemanticFormBuilder.escape_html_entities_in_hints_and_labels = false
Commits on Jul 1, 2010
  1. @yabawock
  2. @yabawock
Commits on Jun 30, 2010
  1. @dusdanig @yabawock

    Fixes: 293 Hint lookup fails when an attribute and model have the sam…

    dusdanig committed with yabawock
    …e name
    
    Added fix in inline_hints_for to see a hash as a blank entry.
    Added spec to test this failure.
Commits on Jun 24, 2010
  1. @pfeiffer
Commits on Jun 9, 2010
  1. @yabawock
Commits on Jun 7, 2010
  1. Changed radio_input and check_boxes_input to no longer uses field_set…

    committed
    …_wrapping_for_method() [which was designed for use with labels that have a mapping to actual inputs]. Instead, I've hard-coded the desired markup into the method. Less DRY, but decoupled.
    
    As a result, we now have control over things like the label(), which no longer contains a `for` attribute for an input that doesn't exist, resolving #253.
Commits on Jun 6, 2010
  1. :input_html can now specify a :size option of nil, resolving #267 wit…

    committed
    …h many thanks to indrekj for the patch.
Commits on May 26, 2010
  1. Reverting two i18n patches pulled in from the rails3 branch which are…

    committed
    … not compatible with Rails 2.3.x.
    
    Specs pass without deprecation warnings, and the relevant commits in Rails (13867a3 and 9bd91b0) seem to be in master, but not in the v2.3.8 branch.
    
    Revert "i18n fix: "The {{key}} interpolation syntax in I18n messages is deprecated. Please use %{key} instead.""
    This reverts commit .
    
    Revert "i18n fix II: "The {{key}} interpolation syntax in I18n messages is deprecated. Please use %{key} instead.""
    This reverts commit 49b45f6.
Commits on May 24, 2010
  1. @HP @yabawock

    i18n fix: "The {{key}} interpolation syntax in I18n messages is depre…

    HP committed with yabawock
    …cated. Please use %{key} instead."
  2. @tjtuom @yabawock

    Translations for nested models.

    tjtuom committed with yabawock
Commits on May 23, 2010
  1. @yabawock
  2. @sobrinho @yabawock
  3. @yabawock
  4. @yabawock

    Mark formtastic outputs as html_safe

    yabawock committed
    Formtastic::Util.html_safe() checks the available environment and marks a string as html_safe appropriately
Commits on May 3, 2010
  1. An input without an :as option will only route to country_input if th…

    committed
    …e method name is /country$/ not /country/ (which is too greedy). Resolves #260
Commits on Apr 24, 2010
  1. @sobrinho
Commits on Apr 22, 2010
  1. belongs_to associations will now render errors attached to the associ…

    committed
    …ation and the column (fixes issue #161)
    
    * previously f.input(:section) would only look to errors[:section]
    * so anything in errors[:section_id] would not be displayed
    * some associations like validates_uniqueness_of need to be done on the column name
    * Formtastic will now also look at errors[:section_id] (or whatever the foreign key is named)
    * we squish all the errors together, make sure they're unique and display them all with the input
Commits on Apr 18, 2010
  1. Changed the behaviour of date/time selects when the object attribute …

    committed
    …has a nil value.
    
    It used to default to Time.now, but since :selected is deprecated you can no longer overrise the Time.now to nil, so we must default to nil instead. Closes issue #240.
Commits on Apr 12, 2010
  1. Reverting class_name additions for belongs_to associations in f26248f

    committed
    …and fe5db0d, as they seemed to optimise for a use case which isn't consistent with Rails' behaviour and most common use case.
    
    See issue 236 for more information, patch welcome that caters to both scenarios adequately.
    
    This reverts commit 6d6f08970f3f5599ee90071885a69d630 and 02a7f797378a2b7415c5ba82bc6007bfe.
    Revert "spec for 'class_name' option on 'belongs_to' associations"
    Revert "fix select input for 'has_many :foos, :class_name => 'FooBar'"
Commits on Apr 11, 2010
  1. @dallas
Commits on Mar 31, 2010
  1. Revert "added currency select input"

    committed
    This reverts commit 4c9dd06.
Commits on Mar 29, 2010
  1. @nickyp
Commits on Mar 13, 2010
  1. @wulffeld
  2. Since we're not planning on support :default going forward, it doesn'…

    committed
    …t make sense to temporarily push people to migrate over to :default. Instead, the next release will just have a different (better) implementation of :selected.
  3. added a deprecation warning for :selected/:checked/:default -- they'l…

    committed
    …l be gone in 1.0 in favor of after_initialize or controller set-ups
Commits on Mar 1, 2010
  1. @timcharper

    make eval'ed code's line-numbers line up

    timcharper committed with
    It just makes debugging easier this way.
  2. @karsthammer
  3. @karsthammer
  4. Better workaround for ActiveRecord's flawed Base.human_name:

    committed
    * affecting commit buttons
    * in 0.9.6 and earlier we called @object.class.human_name, but this resulted in things like "Userpost" instead of "User post"
    * in 0.9.7 we called @object.class.name.underscore.humanize
    * 0.9.6 worked for people with their own i18n for model names (human_name falls back to "Userpost" if there's no i18n)
    * 0.9.7 worked for those without i18n ("User post" instead of "Userpost")
    * the crappy fallback in human_name is the issue we're routing around (@object.class.name.humanize)
    * so we now call @object.class.name.underscore.humanize only if it looks like human_name has fallen back to the crappy @object.class.name.humanize
  5. Radio and checkbox inputs no longer have the legend label associated …

    committed
    …with the first choice's input, resolving #101.
Something went wrong with that request. Please try again.