Thread:Extension talk:TemplateData/Extending TemplateData

(the following message is based on a discussion on Mooeypoo's page in hewiki + some other comments)
 * Meaning for types - it is important to explain in the documentation how long, or how many lines are expected for each type (in general). E.g. content - used for a block of content more than a short paragraph, line - multiple words/short paragraph, string - a word or two. [This doesn't mean there is a requirement for a content to be long, but this is the expectation]. If it doesn't fall into the definition of "type", maybe another parameter should indicate the expected "length".
 * Closed options - sometimes templates requires one of possible closed options . Is it possible to indicate a parameter expect one of possible options?
 * Date type - In many templates the expected parameter is of Date type. Although visualeditor may not be able handle date validation (as sometimes it includes wikilinks, different languages etc) in the near future, it is important to be able to mark a parameter as date type for later use or for eaiser integration with Wikidata. (BTW if you want to validate dates, I would suggest to ask Daniel Kinzler, how wikidata handles dates in different languages - some of the code may be useful for visualeditor)
 * Strict TempalteData - Is it allowed (and is it recommended) to extend TemplateData with custom keys or should it be strict to the definition. For example one may want to define extra key with URL, that an extension script use to validate the parameter.