Template talk:Ticket: Difference between revisions

Template talk:Ticket (view source)

1,190 bytes added , 1 April 2015

→‎encapsulate registration/ticket creation ?: I would rather have many succinctly named templates than one template with named parameters

13,212

edits

@@ Line 5: / Line 5: @@
 we could easily support all main use-cases by combining related templates, e.g. <nowiki>{{Issue Tracker}}</nowiki>, which also encapsulates the registration and ticket creation processes. --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 15:00, 1 April 2015 (EDT)
+: Actually I consider them to have very separate use cases.  I would rather split {{tl|Issue Tracker}} into three separate templates, say {{tl|tickets}} for a link to the page listing the tickets, {{tl|register to sf}} to link to the SourceForge account registration form and {{tl|create ticket}} to link to the ticket creation form.  (I guess the jargon will shift from ''issue'' to ''ticket'' so that {{tl|issue}} will be moved to {{tl|ticket}}.)
+: The bottom line is that I do not particularly like having to use named parameter unless it really is necessary.  I much rather prefer having more templates with more descriptive names with only unnamed parameters.  One could of course have four separate templates using a meta template, but then one would have to maintain five templates instead of four.
+: Additionally the templates should preferably link to each other in the related templates section.  They would then not have gathered up in one single template with a slightly ambiguous name (when used in running text) for the sake of maintenance.
+: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 18:58, 1 April 2015 (EDT)