Ticket #376 (closed Defect: fixed)
Association types get no workspace assignment
Reported by: | jri | Owned by: | jri |
---|---|---|---|
Priority: | Major | Milestone: | Release 4.1 |
Component: | DeepaMehta Standard Distribution | Version: | 4.0.12 |
Keywords: | Cc: | dgf, Malte, JuergeN | |
Complexity: | 2 | Area: | |
Module: | deepamehta-workspaces |
Description
Change History
comment:2 Changed 12 years ago by Jörg Richter
- Status changed from accepted to closed
- Resolution set to fixed
Fix: assoc types get workspace assignment (#376).
Analogous to topic types:
- interactively created association types are assigned to the current workspace.
- association types created through migrations are assigned to the default workspace ("DeepaMehta"), provided they belong to the "dm4" URI namespace. For other namespaces *no* workspace assignment is done automatically. In that case workspace assigment is up to the (3rd-party) developer.
BREAKING CHANGES
Public Workspaces API:
- getWorkspaces() is renamed to getAssignedWorkspaces(). ### You must adapt your plugins
- assignTypeToWorkspace() is new method. It assigns a type *and* all its view configuration topics to a workspace.
Close ticket 376.
Note: See
TracTickets for help on using
tickets.