Form containers¶
- References
- class crispy_forms_foundation.layout.containers.Fieldset(legend, *fields, css_class=None, css_id=None, template=None, **kwargs)[source]¶
Bases:
FieldsetIt wraps fields in a
<fieldset>:Fieldset("Text for the legend", 'form_field_1', 'form_field_2' )
The first parameter is the text for the fieldset legend. This text is context aware, so you can do things like :
Fieldset("Data for {{ user.username }}", 'form_field_1', 'form_field_2' )
- class crispy_forms_foundation.layout.containers.Container(name, *fields, css_id=None, css_class=None, template=None, active=None, **kwargs)[source]¶
Bases:
ContainerOverrides original Container element to get the “active” classname from Class attribute
active_css_classso it’s compatible with Foundation 5 and 6.
- class crispy_forms_foundation.layout.containers.ContainerHolder(*fields, css_id=None, css_class=None, template=None, **kwargs)[source]¶
Bases:
ContainerHolder
- class crispy_forms_foundation.layout.containers.TabHolder(*fields, css_id=None, css_class=None, template=None, **kwargs)[source]¶
Bases:
TabHolderTabs holder object to wrap Tab item objects in a container:
TabHolder( TabItem('My tab 1', 'form_field_1', 'form_field_2'), TabItem('My tab 2', 'form_field_3') )
TabHolderdirect children should allways be aTabItemlayout item.A random id is builded for the tab holder if you don’t define it using
css_idargument.The first
TabItemcontaining a field error will be marked as active if any, else this will be just the firstTabItem.
- class crispy_forms_foundation.layout.containers.VerticalTabHolder(*fields, css_id=None, css_class=None, template=None, **kwargs)[source]¶
Bases:
TabHolderVerticalTabHolder appends vertical class to TabHolder container
- class crispy_forms_foundation.layout.containers.TabItem(name, *fields, css_id=None, css_class=None, template=None, active=None, **kwargs)[source]¶
Bases:
ContainerTab item object. It wraps fields in a div whose default class is “tabs” and takes a name as first argument.
Tab item is also responsible of building its associated tab link with its
render_linkusing thelink_templateattribute.Example:
TabItem('My tab', 'form_field_1', 'form_field_2', 'form_field_3')
TabItemlayout item has no real utility out of aTabHolder.
- class crispy_forms_foundation.layout.containers.AccordionHolder(*accordion_groups, css_id=None, css_class=None, template=None, **kwargs)[source]¶
Bases:
AccordionAccordion items holder object to wrap Accordion item objects in a container:
AccordionHolder( AccordionItem("group name", "form_field_1", "form_field_2"), AccordionItem("another group name", "form_field"), )
AccordionHolderdirect children should allways be aAccordionItemlayout item.A random id is builded for the accordion holder if you don’t define it using
css_idargument.The first
AccordionItemcontaining a field error will be marked as active if any, else this will be just the firstAccordionItem.
- class crispy_forms_foundation.layout.containers.AccordionItem(name, *fields, css_id=None, css_class=None, template=None, active=None, **kwargs)[source]¶
Bases:
AccordionGroupAccordion item object. It wraps given fields inside an accordion tab. It takes accordion tab name as first argument.
The item name is also slugified to build an id for the tab if you don’t define it using
css_idargument.Example:
AccordionItem("group name", "form_field_1", "form_field_2")