Forms
Editing Records
The editing of records is a key component of any OPAL application. A key pattern is to edit
or create an individual record in a modal containing the form for just that record. OPAL provides
the Angular Controller opal.controllers.EditItemCtrl
for doing just this
Form and modal templates
Subrecords have get_form_template()
and get_modal_template()
methods, which are used for
figuring out how to render forms for interacting with them. These use the following template
paths based on the context in which they are called:
# Forms
forms/{episode_type}/{list slug}/{record_name}_form.html
forms/{list_slug}/{record_name}_form.html
forms/{episode_type}/{record_name}_form.html
forms/{record_name}_form.html
# Modals
modals/{episode_type}/{list slug}/{record_name}_modal.html
modals/{list_slug}/{record_name}_modal.html
modals/{episode_type}/{record_name}_modal.html
modals/{record_name}_modal.html
Autogenerating forms
The opal
commandline tool has a scaffold command, which will autogenerate missing form templates
for subrecord models. Simply run the following command to generate.
$ opal scaffold $DJANGO_APP_WHERE_MODELS_LIVE
(Note this will also generate and run migrations for any unmigrated models.xb)
Client side Validation
Client side validation for forms requires a pattern and a help block && uses ng-pattern, ng-disabled (https://docs.angularjs.org/api/ng/directive/input)
Helpers
OPAL contains a number of helpers for developing forms and input modals.
Many of these are located in the forms template tag library, which is a Django templatetag library that understands the context of common patterns with OPAL for creating forms and modals.
It provides helpers for various input types that will allow you to render consistent forms, with less verbose templates.
{% load forms %}
<form class="form-horizontal">
{% input "autofocus" label="Destination" model="editing.destination" lookuplist="destination_list" %}
{% datepicker label="Date" model="editing.date" %}
{% checkbox label="Alone?" model="editing.alone" %}
</form>
For full documentation of the options, please see the Form templatetags reference material