Removes call to config option through explicit classname

[chrp]

ActiveAdmin relies on a subclassing FormBuilder. For remotely related reasons I also need to set the skipped_columns option only for that subclass but the explicit call to Formtastic::FormBuilder.skipped_columns here prevents me from doing that.

General question: Should I be able to copy the config when subclassing from FormBuilder to be able to alter it's behaviour? Or should there be only one global config.

For my very specific problem: Removing the explicit reference to the class actually works quite fine (except that a future dev might have trouble finding out where skipped_columns came from)

[mikz]

This looks like a very reasonable change. The change that introduced it (d3814b4) did not count that the inputs are actually included to the form builder anyway.

Could you cover it with a test?

[chrp]

Happy to cover it with a test of cause. Does it make sense to subclass FormBuilder and test that I can change the setting for that subclass? Or what should the test cover in your eyes?

[mikz]

The test could cover that a subclass can have different skipped columns than the parent class (FormBuilder). So yeah, creating a subclass and setting the skipped_columns property, then verifying it does not render those columns.

[mikz]

Thank you!