Code

Opened 7 years ago

Closed 7 years ago

#4818 closed (fixed)

Databrowse - missing step?

Reported by: kevin@… Owned by: adrian
Component: contrib.databrowse Version: master
Severity: Keywords: databrowse
Cc: Triage Stage: Design decision needed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

First, THANK YOU, THANK YOU -- I love Django!

Step 2. READS:
from django.contrib import databrowse

databrowse.site.register(SomeModel)
databrowse.site.register(SomeOtherModel)

I think instead of:
from django.contrib import databrowse

maybe it should read:
from someapp.models import *

Where 'someapp' is the name of the application. The documentation includes in step 3. the directive:
from django.contrib import databrowse

Attachments (0)

Change History (3)

comment:1 follow-up: Changed 7 years ago by SmileyChris

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Triage Stage changed from Unreviewed to Design decision needed

It's still important to import databrowse in step two, but perhaps it could read:

from django.contrib import databrowse
from myapp.models import SomeModel, SomeOtherModel

databrowse.site.register(SomeModel)
databrowse.site.register(SomeOtherModel)

I'm unsure if it's really necessary though.

comment:2 in reply to: ↑ 1 Changed 7 years ago by miguel.filho@…

I think it's nice this way.

comment:3 Changed 7 years ago by adrian

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

(In [5866]) Fixed #4818 -- Improved 'Step 2' example in docs/databrowse.txt. Thanks, kevin@…

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.