Code

Opened 5 years ago

Closed 5 years ago

#10135 closed (fixed)

Widgets documentation

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

Description

Could you publish the namescape in which widgets reside.

I'm still trying to find it, and it's very frustrating when the official dosc don't help.

Attachments (2)

10135.diff (986 bytes) - added by Rob Hudson <treborhudson@…> 5 years ago.
Adding import to documentation in the first case that uses forms
10135.2.diff (987 bytes) - added by Rob Hudson <treborhudson@…> 5 years ago.
Typo in last diff.

Download all attachments as: .zip

Change History (4)

comment:1 Changed 5 years ago by Rob Hudson <treborhudson@…>

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset

While the topics/forms/index.txt file shows the "from django import forms" statement in code, apparently none of the other docs do, which might be the confusing here?

Changed 5 years ago by Rob Hudson <treborhudson@…>

Adding import to documentation in the first case that uses forms

Changed 5 years ago by Rob Hudson <treborhudson@…>

Typo in last diff.

comment:2 Changed 5 years ago by adrian

  • Resolution set to fixed
  • Status changed from new to closed

(In [9853]) Fixed #10135 -- Added some import statements to docs/ref/forms/fields.txt and docs/ref/forms/widgets.txt to help people understand where the code lives. Thanks, Rob Hudson

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.