-
Notifications
You must be signed in to change notification settings - Fork 134
Customizing form-groups #65
Comments
This is what I came up with. I didn't fork a version because I want to keep the composer dependency to your updates while still keeping my changes (in a child class):
|
Hey, thanks for taking the time to put this together. I understand there can be a need to customise different parts of the "form-group" and this library doesn't expose great control over them, but I'm not sure this is the direction I'd want to go. Introducing another options array makes it harder to see what's going on, and appending to class names when the rest of the library overrides them would just be confusing for develops. I know this isn't the answer you're after and I apologise. To be honest, this package is long overdue for a complete overhaul and I just haven't had time to do it. I still try to maintain it whenever I can but I'm hesitant to continue development in it's current state. I would encourage you to fork (or just override in your own app) to get the package working the way you need. Again, thanks for putting this together and I'm sorry for the delay in responding. I'll keep this ticket open as a feature to consider if there ever becomes a major new version. |
It would be nice if I could pass a parameter to my input fields to add an additional class to the form-group wrappers, such as styling multiple columns (this IS bootstrap, afterall), like so:
'div' would take an array, but if it's a string, assume we are assigning to the 'class' attribute. GetFormGroupOptions supports passing $options as a 2nd parameter, but it's not used anywhere! I'd suggest that 'class' be appended to rather than overwritten. Always add form-group along with whatever classes they want.
The text was updated successfully, but these errors were encountered: