Template talk:Incorrect

From Rosetta Code

parameter for reason

Can we add a parameter to this template that allows the user to note why he thinks the solution needs review? At the moment, if one catches the template when it's added, or within in a few days, because it's usually related to a change in task specifications (and usually applied to every language on a page after a spec change).

But if you're reviewing the "Tasks needing attention list", or happen to come across the template months after it's added, the context is lost, and it's not clear WHY the task "needs review", and having to do a detailed analysis is demotivating.

--DanBron 19:32, 1 December 2009 (UTC)

The parameter is already there, but it seems people don't use it sometimes. There's no real way of making it "required" (a "{{{1}}}" would show instead of a reason if we didn't check for the parameter's existence), so I think the best we can do is try to make it really obvious that the option is there and nice to use. --Mwn3d 23:39, 18 April 2010 (UTC)

What about example needs attention?

The example needs attention template is missing. In some cases this is more desirable than using incorrect, especially where the example works but may not be the best example.


--Dgamey 22:08, 18 April 2010 (UTC)