Code

Opened 5 years ago

Closed 5 years ago

#11099 closed (invalid)

Working with forms example code - possible typo

Reported by: TomA Owned by: nobody
Component: Documentation Version: master
Severity: Keywords:
Cc: tomovo@… Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

In the chapter "Working with forms", subchapter "Customizing the form template", the 3rd code example that deals with looping over the form's errors seems to be trying to loop over items of form.subject.errors. Shouldn't that loop over form.errors instead? That's what works for me at least.

Attachments (0)

Change History (1)

comment:1 Changed 5 years ago by mattmcc

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Resolution set to invalid
  • Status changed from new to closed

Nope. Each form field has its own errors collection.

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.