sharks

get started

concepts

features

syntax

 

monkeys

intro

mods

REST API

 

platypuses

github

blueprints

tickets

 

everyone

support

ideas

contact

license

 

 
 

setting card plus *type plus *content to type Pointer gives error

help edit space_dashboard

Support Ticket

setting card plus *type plus *content to type Pointer gives error+status
help edit space_dashboard
answered
setting card plus *type plus *content to type Pointer gives error+tags
 

setting card plus *type plus *content to type Pointer gives error+issues

help edit space_dashboard

I set a my_card+*type+*content to type:Pointer (using the select menu when initially creating that plus card from the my_card+*type card), and I got the message "Application error. Oh, Man [sic]. You found a hitch in the Wagn". Below the error message, the +*content card appeared successfully transformed into a Pointer. You may ask "Why was I doing that in the first place?" Because I was trying to figure out how to make a plus card appear as a Pointer the first time it's edited, which I found another way to do.

 

help edit space_dashboard

So the card "my_card+*type+*content" would set the content for all the cards that have the type "my_card".  If my_card is not a cardtype, there should be an error, because "my_card+*type" is basically a nonsense set -- the set of all cards of a type that doesn't exist.  Obviously the error messaging needs improvements -- it should be more elegant and informative than a generic "hitch".  I don't think we currently have anything catching impossible sets like that.

 

I think what you were going for may have been more like "my card+*right+*default".   That tweaks both the Set and the Setting:

 

  1. the set should be my_card+*right because that refers to all the cards that end in +my_card.
  2. the setting should be *default, because that just determines the initial type/content for new cards, whereas *content continues to template a card's content long after it's been created.
PS, thanks for the subtle "sic" cue.  I went ahead and lowercased "Man" in the code for the next release.  It's evidently been that way at least since we moved to git from subversion in 2007.