You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it would be cool if we added the option to use floating fields by default on all <input> fields throughout an entire project. Maybe there is a better way to do it, but I was thinking we could add a boolean Django setting CRISPY-FLOATING-FIELDS. And (maybe one day) add a helper attribute that would allow for overriding the setting on a per-form basis.
I'm a little uncertain if my idea aligns with crispy-bootstrap5's plans, considering the introduction of field groups in Django 5.0. I'm interested in people's thoughts about this feature, if a PR would be accepted, and how it would integrate with future plans for this package? Thanks!
The text was updated successfully, but these errors were encountered:
Seconded! Generally if you're going to use floating fields it's going to be for all fields as part of the design rather than a single floating field so it makes sense to have this as a default option.
Seconded! Generally if you're going to use floating fields it's going to be for all fields as part of the design rather than a single floating field so it makes sense to have this as a default option.
Default no... as floating fields are huge... however, a single option, rather than having to use a Layout would be great for when you do whant to do this.
I think it would be cool if we added the option to use floating fields by default on all
<input>
fields throughout an entire project. Maybe there is a better way to do it, but I was thinking we could add a boolean Django settingCRISPY-FLOATING-FIELDS
. And (maybe one day) add a helper attribute that would allow for overriding the setting on a per-form basis.I'm a little uncertain if my idea aligns with crispy-bootstrap5's plans, considering the introduction of field groups in Django 5.0. I'm interested in people's thoughts about this feature, if a PR would be accepted, and how it would integrate with future plans for this package? Thanks!
The text was updated successfully, but these errors were encountered: