-
Notifications
You must be signed in to change notification settings - Fork 296
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: Switching between classes by theme #687
Comments
Sounds good. Sounds like a PR! |
Do you think we should always not include |
Eh? Do you mean |
I would like to change the view file as well for each Theme. return [
'themes' => [
'default' => [
// ...
'template_prefix' => 'laravel-form-builder::',
],
'foo' => [
// ...
'template_prefix' => 'forms.foo.',
],
],
// ...
];
|
I don't get it. What is It's dangerous to change the entire config structure. That would probably break bc. |
So it is not PR, it's issue. If it is difficult to change only class, as in the case of Horizontal form, it is necessary to change view files. I currently use |
I use form and row classes and custom CSS to do different layouts. There's many ways to do this. And every dev can do them. How much effort do you want to put into themes that won't work for everyone, but have to work for more than just yourself? |
But Symfony form can change view files by theme. |
This form builder isn't much like Symfony anymore. But you can PR anything you like, and if it's backward compatible, we might add it. That's the most important IMO: backward compatible. |
I would like to have the ability to set a Theme for each form and switch the classes, etc. listed in the config.
The text was updated successfully, but these errors were encountered: