joelmoss / dynamic_form Goto Github PK

View Code? Open in Web Editor NEW

This project forked from rails/dynamic_form

193.0 10.0 71.0 168 KB

Helpers to deal with your model backed forms in Rails3

Home Page: http://developwithstyle.com/dynamic_form/

License: MIT License

Ruby 100.00%

dynamic_form's Introduction

DynamicForm

DynamicForm holds a few helpers method to help you deal with your Rails3 models, they are:

input(record, method, options = {})
form(record, options = {})
error_message_on(object, method, options={})
error_messages_for(record, options={})

It also adds f.error_messages and f.error_message_on to your form builders.

Read /lib/action_view/helpers/dynamic_form.rb for details of each method.

DynamicErrors

DynamicForm also includes DynamicErrors, which is a port of the custom-err-messages plugin, but built to work with Rails3. It gives you the option to not have your custom validation error message prefixed with the attribute name. Ordinarily, if you have, say:

validates_acceptance_of :accepted_terms, :message => 'Please accept the terms of service'

You'll get the following error message:

Accepted terms Please accept the terms of service

This plugin allows you to omit the attribute name for specific messages. All you have to do is begin the message with a '^' character. Example:

validates_acceptance_of :accepted_terms, :message => '^Please accept the terms of service'

Nigel Ramsay added the ability to specify a proc to generate the message.

validates_presence_of :assessment_answer_option_id, 
  :message => Proc.new { |aa| "#{aa.label} (#{aa.group_label}) is required" }

which gives an error message like: Rate (Accuracy) is required

Installation

DynamicForm can be installed as a gem in your Gemfile:

gem 'dynamic_form'

or as a plugin by running this command:

rails plugin install git://github.com/joelmoss/dynamic_form.git

dynamic_form's People

Contributors

Stargazers

Watchers

dynamic_form's Issues

boolean input string not 'raw'

displays as string, rather than rendered html:

Way to specify which validation errors can be shown?

For example, if you don't want to show "login invalid" or "password invalid" but you would like to show "Account not activated" ...?

error_messages_for is escaping html

I'm using error_messages_for on my forms but it's escaping the html like so: http://cl.ly/DlDN

This is the code I'm using:

<%= error_messages_for(:form, :user, :message => "<strong>Opps, it doesn't look like you filled everything out properly.</strong><br>
            The fields marked in RED below must be filled out properly before you can continue.") %>

Anything I'm missing to get this to work properly? As you can see the input fields with the fieldWithErrors is also escaping html for some reason.

Thanks!

POROs and `@#<PORO>' is not allowed as an instance variable name

Not really an issue as I solved it, but something to note for other users of dynamic_form.

I was implementing dynamic_form with a Plain Old Ruby Object that includes ActiveModel::Validations, and was getting the error in the subject line when trying to use <%= f.error_messages %>.

I didn't find any other instances of this issue, but it can be solved by defining to_model in the PORO:

class Download
  include ActiveModel::Validations
  attr_accessor :name
  validates_presence_of :name

  def to_model
    self
  end
end

Thanks for the gem, works great.

Skip header, body etc

Hi,

Is there a way to simply skip activerecord.errors.template.header, activerecord.errors.template.header.body and display only error messages with f.error_messages ?

Does it support rails4 in future?

form helper does not work with Rails 3.0.7

I don't know at what point the form helper stopped working so I'm just going to say it doesn't work on 3.0.7 as that's the version I'm running on.

I have a nested model (although I tried this with a non-nested model and got the same problem) called Employer::Question. I created a haml form for the new view and called:

= form('question')

Reloading the page threw the error that Rails couldn't find the route :action => "employer/questions", :controller => "employer/questions".

I dug into the code some and it looks like the form method is expecting url_for to return the action name ("create" for example). But it's actually returning the path for the action ("employer/questions" in my case).

Changing the call to form_for to:

contents = form_tag(action, :method =>(options[:method] || 'post'), :enctype => options[:multipart] ? 'multipart/form-data': nil)

seems to fix the problem but all the tests break because the overridden url_for still returns the action. I don't know how to fix the tests so I haven't sent a pull request. I'm sorry for that.

oops

never mind

Gem is slow to load

I have been trying to shorten my Rails app startup times, so I benchmarked the gem requirement times using the trick described at http://stackoverflow.com/questions/9505612/slow-loading-time-for-rails-3-2-debug-shows-rails-loading-twice.

I found dynamic_form to be the slowest-loading gem next to Devise (which notoriously slow-loading).

Any idea why the loading of dynamic_form is so slow and how to speed it up?