Opened 2 years ago

Closed 2 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


Provide a way to unregister a given model from AppConfig.

Change History (3)

comment:1 Changed 2 years ago by aaugustin

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

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?

Last edited 2 years ago by aaugustin (previous) (diff)

comment:2 Changed 2 years ago by mitar

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 Changed 2 years ago by aaugustin

  • Resolution set to wontfix
  • Status changed from new to 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".

Note: See TracTickets for help on using tickets.
Back to Top