Idea
Create Type for Inclusions+issues
As a Wagneer, I want to specify the default type for Pointer items created from the missing link. In the Pointer case, there is no place to put the desired type in the pointer card, so we want to be able to specify it with inclusion syntax.
Create Type for Inclusions+solution
At a higher level the desired feature might involve having an options set {type:Cardtype}, but with an 'Add New' extra options to type the name of a new or existing card to add. When it is new, the syntax in the example can cause the new card to get the right type.
Create Type for Inclusions+example
I tried this on gerry.wagn.org, and didn't really expect it to work, but it would have been cool if it did. I added this in a page:
{{Flow Types|view:titled;type:Pointer|type:Cardtype}}.
It creates the Pointer card as desired, then I add a few names of not yet existing cards to the list and I would like the Add links to use the type:Cardtype spec as the default type. I know why it probably wouldn't work currently, but maybe it is a good behavior for this case and others.
Hmm, found another case where you might expect a type:X in inclusion syntax to have an effect.
The case is a *structure rule, eg http://gerry.wagn.org/Scale+*type+*structure which contains {{+field|type:Field}}. That one seems less of an edge case than the main case in this ticket.
Feel free to assign tickets like this that I report for me to find a code fix. I don't want to fix anything you don't consider broken, but it it is a low priority ...
Update: this new case only seems to be broken for a user declared type (Field, recently created if that matters, vs. Phrase later in the *structure rule.
D'oh, maybe it is working, it just shows as a basic type because the new type doesn't have any rules that would change that.
We aren't able to nest multi-edits, are we. Now I want to see what happens.
Create Type for Inclusions+discussed in support tickets
Create Type for Inclusions+relevant user stories