…, better fix is to use Timecop or similar
…avour of a deprecated :selected option (issue #152): * if the object has a value, we should pre-select that at all times, ignoring the :default option * if the object has no value, and :default is provided as a Date/Time then :default should be pre-selected * if the object has no value, and :default is provided as nil then no option should be pre-selected (it will default to the first) * if the object has no value, and :default is not provided then fallback to Time.now (or perhaps a configurable default) * :selected invokes a deprecation warning, but is an alias of :default * it's not a real deprecation, as the behaviour has changed with all the bugs and half-fixes
…we can make it easier for people to upgrade when/if we add in new stylesheets (like an IE-only stylesheet, for example).
…just formtastic.rb, although it really doesn't matter what it's called
… up. Now works in my test-project - confusing to spec this one just for a certain plugin. Closing #155.
… with the bundle. Closing #151.
Signed-off-by: TMaYaD <firstname.lastname@example.org>
Broken: Namespaced::Post -> namespaced/post Fixed: Namespaced::Post -> namespaced_post
* added failing specs * changed date_or_datetime_input to only fallback to Time.now when options[:selected] is not present
…s a activerecord object. Otherwise delegates to activerecord. Signed-off-by: José Valim <email@example.com>
…od now being global not just for non-activerecord objects." This reverts commit 99cdf67.
…ttribute_name removed in favor of humanize. label_str_method now honored if provided and no label or i18n text present." This reverts commit 863e3ff. Conflicts: spec/input_spec.rb
…eing global not just for non-activerecord objects.