Opened at 2010-02-17T03:14:36Z
Last modified at 2022-10-21T22:41:29Z
#539 new todo
identify access points to model mutations
| Reported by: | Ichthyostega | Owned by: | Ichthyostega |
|---|---|---|---|
| Priority: | normal | Milestone: | 0integration |
| Component: | lumieraSteam | Keywords: | interfaces design session |
| Sub Tickets: | #300 | Parent Tickets: | #319, #412, #542 |
Description (last modified by )
Question is how exactly to relate the discovery API to the possibility of performing mutations on the model. It is clear that those mutations will go through the command frontend (and from there to the SteamDispatcher)
- identify the preferable points where to invoke those commands
- consider ways how to link in the arguments automatically from the given context
- investigate if hard-wiring is acceptable — or do we need some kind of binding?
Change history (3)
comment:1 by , at 2010-02-22T01:05:27Z
| blocking: | 319, 412 → 319, 412, 542 |
|---|
comment:2 by , at 2022-10-21T22:41:29Z
| Description: | modified (diff) |
|---|
comment:3 by , at 2025-12-25T00:00:00Z
| blockedby: | 300 |
|---|---|
| blocking: | 319, 412, 542 |
| Parent Tickets: | → 319, 412, 542 |
| Sub Tickets: | → 300 |
Note:
See TracTickets
for help on using tickets.

Migration MasterTickets ⟼ Subtickets-plugin