Display role vocabulary, migration commit fix, stale enforcement reports
This commit is contained in:
@@ -51,7 +51,12 @@ from shopdb.core.models import (
|
||||
# Display-role mapping (which kiosk shows which surface). On the surface
|
||||
# because a plugin reporting on displays has no other way to name what a
|
||||
# display IS - the role lives in core, not in any plugin.
|
||||
from shopdb.core.models.dashboarddefault import DashboardDefault
|
||||
from shopdb.core.models.dashboarddefault import (
|
||||
DashboardDefault,
|
||||
DISPLAY_ROLES,
|
||||
DISPLAY_ROLE_PATHS,
|
||||
normalize_display_role,
|
||||
)
|
||||
|
||||
# Response + pagination helpers for plugin API blueprints
|
||||
from shopdb.utils.responses import (
|
||||
@@ -259,6 +264,12 @@ __all__ = [
|
||||
'OperatingSystem',
|
||||
'AssetRelationship',
|
||||
'RelationshipType',
|
||||
# Display roles. The role vocabulary is the kiosk's own, so a plugin that
|
||||
# reads a reported display type resolves it the same way core does.
|
||||
'DashboardDefault',
|
||||
'DISPLAY_ROLES',
|
||||
'DISPLAY_ROLE_PATHS',
|
||||
'normalize_display_role',
|
||||
# Response + pagination helpers
|
||||
'success_response',
|
||||
'error_response',
|
||||
|
||||
Reference in New Issue
Block a user