Opened 11 years ago
Closed 11 years ago
#21698 closed New feature (wontfix)
Provide a way to unregister a given model from AppConfig
Reported by: | Mitar | Owned by: | nobody |
---|---|---|---|
Component: | Core (Other) | Version: | 1.6 |
Severity: | Normal | Keywords: | app-loading |
Cc: | mmitar@… | Triage Stage: | Unreviewed |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Provide a way to unregister a given model from AppConfig.
Change History (3)
comment:2 by , 11 years ago
This is related in some way to #21699. So there are two ways to allow making custom subclasses of models which should not be registered. One is to somehow allow some configuration in Meta
(#21682), another is to call current metaclass which adds it, but be able to remove it from registry immediately afterwards (a bad side-effect is that registration signal has been already made).
comment:3 by , 11 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Let's keep the discussion in #21699 -- I'd rather not split it across two tickets.
The provisional answer to this particular request is "there's no public API to register or unregister models with the app registry".
The fact that models are registered is a private implementation detail that isn't described anywhere in the documentation.
What would be the intended effect on public APIs?