Model Types

Open Stories and Issues

Can't edit a field of a Model Value: Create a Model Type, MT, with field F and F2. Create a Parent thing P, and give it a Model Property based on MT, MTP. In P, try to edit F directly: [[MTP -> F._edit]]. It simply doesn't work.
Drag-and-drop reordering probably doesn't work in Model Types yet: Not tested yet, but I suspect that rearranging a List inside of a Model Value probably doesn't work in the new Client.
Editing Lists of Model Type doesn't work right in old-style Editor: In Read Access is much too leaky, the top Task was accidentally deleted right after I created it, but seems to have taken anyway. Now, it's just stuck there: I can't delete it, move it, or anything.
I should be able to construct a Model Value in code: This is the thin end of a wedge, but I really want to be able to specify, eg, a Duration of 2 years inline in the Carolingian Officers' Space. At the moment, I have to construct pointless Things just to hold values that I am using in code.
Illegal XML in Model's Instance Edit View causes Model Property rendering to crash: Suffice it to say, when we render a Model Type for editing, it can't cope with malformed XML in text.
Optional Model Values don't work right: Create a Model, with a Text field. Then, in another Thing, create an Optional Property derived from that Model. Fill in the text field. Restart the server -- the value is not correctly persisted.
Sub-lists don't appear to be working: In my Recipes Space, try adding a Variation to Bacon Candy. That works, but I can't add anything to its Shopping List!
There is no way to remove a dead field from an element of a List of Model Type: This is rare, but can come up -- it's a design bug.

Closed Stories and Issues

_refs doesn't pick up references from Model Properties: If I have a Link Set defined in a Model Property, and then set Links in a Thing that uses that Property, _refs doesn't pick it up.
From a Model Value, I should be able to access the enclosing Thing: This is a subtle but significant problem pointed out by Eric. Sometimes, when you are building a sophisticated Model Type, you really want to be able to access contextual information that exists on the enclosing Bundle. For example, in his highly-customized Review Types, he wants to be able to display the current Average -- but the Average Property is on the Thing, not on the Review, and the Review currently has no way of getting to the enclosing Thing, even in workaround.
I can create multiple Types from the same Model: Currently, it is extremely easy to accidentally create multiple Types from the same Model. This is usually undesireable, and probably always a mistake. So let's plan to disable this for the time being, and we'll re-enable it if anybody comes up with a compelling use case.
Summary showing up twice in Tasks: See this issue for an example of the problem. Go into the Editor, and look at the Tasks. Each one is display the Summary property twice.