#33163 closed Cleanup/optimization (fixed)
Add AppConfig.ready() example to the admonition about connecting receiver functions.
| Reported by: | Roxane | Owned by: | Roxane |
|---|---|---|---|
| Component: | Documentation | Version: | 3.2 |
| Severity: | Normal | Keywords: | signals appconfig |
| Cc: | Adam Johnson | Triage Stage: | Ready for checkin |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
See https://forum.djangoproject.com/t/load-signals-automatically/9666
My original idea was to import automatically everything in the submodule signals to avoid wondering why the signals do not work. Finally, we setted on detailling the documentation, expanding the "Where should this code live ?" note and including a sample AppConfig
Change History (7)
comment:1 by , 3 years ago
comment:2 by , 3 years ago
| Cc: | added |
|---|---|
| Keywords: | appconfig added; documentation app config removed |
| Patch needs improvement: | set |
| Summary: | Detail how to connect signals → Add AppConfig.ready() example to the admonition about connecting receiver functions. |
| Triage Stage: | Unreviewed → Accepted |
Thanks for this suggestion. I agree that AppConfig.ready() example would be helpful, but I don't think a separate section is needed.
comment:3 by , 3 years ago
| Patch needs improvement: | unset |
|---|---|
| Triage Stage: | Accepted → Ready for checkin |
Note:
See TracTickets
for help on using tickets.
You can find the PR