2 customisation options for has_many form

[developer88]

Added :title => false and :new_record => false to prevent adding h3 block and 'New object' button for has_many form

[seanlinsley]

I'm confused, what are you trying to achieve with this? Could you provide before & after screenshots?

[developer88]

Showing h3 title

Showing Add button

Not showing h3 title

not showing Add button

so i have a form with:
f.has_many :translations, :title => false, :new_record => false do |translation|
so with my options i can turn off showing h3 Title because i don't need it and not showing add button which i don't need either.

I think, one of this options can be useful for someone else too.

[seanlinsley]

Perhaps this is a better way to write the changes:

# at the top of the method definition:
options = { :for => association, :title => true, :new_record => true }.merge(options)

# then the actual code
if options[:title]
  title = object.class.reflect_on_association(association).class_name.human(:count => 1.1)
  form_buffers.last << template.content_tag(:h3, title)
end

inputs options, &form_block

form_buffers.last << js_for_has_many(association, form_block, template).html_safe if options[:new_record]

Note that I changed klass.model_name to the more succinct class_name

... @gregbell, is it possible to use Arbre here? I hate to force the title part to live on four lines instead of one.

[developer88]

With your changes i got tons of errors in specs:

with class_name and i 've got errors for spec if we do not add anything to form_buffers.last

[seanlinsley]

Really? class_name works fine for me.

The form_buffers.last problem is likely that with my changes, the function will return nil instead of the form buffer if new_record is false.

[developer88]

1. with class_name i've got ' undefined method `human' for "Post":String' in specs.

2. with form_buffers changes you advise - because of form_buffers.pop (why?) it is not rendering first element inside has_many block:
   spec failed: Failure/Error: body.should have_tag("label", "Title 1")

[seanlinsley]

By the way, you need to rebase on master.

git pull --rebase upstream master

Specifically, the onclick string in js_for_has_many has been updated (un-broken, really)

[developer88]

@daxter i've updated my forked repo.

[macfanatic]

#2068 was just merged in that added the title functionality. Could you rebase this to just include your new option to hide the "add" button?

[developer88]

Sure, but... please, tell me how :)

[macfanatic]

First, start by rebasing your feature branch off of the master branch from upstream (gregbell/active_admin).

git pull --rebase upstream master

If you don't have upstream as a remote, you can add it with:

git remote add upstream git://github.com/gregbell/active_admin.git

Then resolve conflicts as they arise when your commits are re-applied as new ones on master, like you had just done the work today. You'll need to remove the code that is no longer needed, since master now has the functionality for specifying a title.

When you're done, force push your feature branch and we'll see the changes in this PR.

git push origin +master

In general, you should create a branch in your fork & submit that branch as a PR to master over here. That way you can pull new changes from our master back into your forked repo's master at any time in the future.

[seanlinsley]

Closing this due to inactivity. @developer88 if you still want to add in the option to disable the "add" button, please create a new pull request.