Opened 17 years ago
Closed 17 years ago
#7328 closed (wontfix)
move max_length error box to step where error actually occurs
Reported by: | debharper | Owned by: | nobody |
---|---|---|---|
Component: | Documentation | Version: | dev |
Severity: | Keywords: | max_length error | |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
The amount of detail of the documentation is excellent. My problem stems from the organization of the parts of the documentation. I am new to django -- working through the tutorial step by step. After editing models.py, I read the box about errors about max_length. At that time it didn't seem to apply to me. After carefully reading another screen-worth of information, I executed the command "python manage.py sql polls" and encountered the error. I think the documentation would be improved by moving the box about the max_length error down below the python command that causes it.
The error is next to the example of code that calls it. Moving it could be counter-intuitive for others.