Opened 11 years ago
Closed 10 years ago
#24322 closed Cleanup/optimization (wontfix)
Increase consistency in the app registry
| Reported by: | Aymeric Augustin | Owned by: | Aymeric Augustin |
|---|---|---|---|
| Component: | Core (Other) | Version: | dev |
| Severity: | Normal | Keywords: | app-loading |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
As a follow-up to #21680, we should improve the implementation of the app registry to ensure that set(self.all_models) in set(self.app_configs).
Change History (4)
comment:1 by , 11 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 11 years ago
| Keywords: | app-loading added |
|---|
comment:4 by , 10 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | assigned → closed |
This ticket was just about simplifying the implementation, not about changing some behavior.
There's no obvious way to move it forwards.
Note:
See TracTickets
for help on using tickets.
It's tempting to replace
Apps.all_modelsby the combination ofApps.app_configsandAppConfig.modelsbut this isn't possible because ofset_available_apps.Indeed, if it's used to add an application temporarily, the
AppConfigfor this application will be thrown away inunset_installed_apps. If it's used again to add the same application, there's no way to know which models belong to this app, unless the list has been stored somewhere likeApps.all_models.