Module talk:Yesno
Testcases and documentation
{| class="wikitable" |+ Test Cases (via [[Template:Yesno/doc]]) |- ! Module output ! Template output ! Expected |- | {{#invoke:Yesno|yesno|yes}} | {{yesno|yes}} | yes |- | {{#invoke:Yesno|yesno|YeS}} | {{yesno|YeS}} | yes |- | {{#invoke:Yesno|yesno|Y}} | {{yesno|Y}} | yes |- | {{#invoke:Yesno|yesno|y}} | {{yesno|y}} | yes |- | {{#invoke:Yesno|yesno|no}} | {{yesno|no}} | ''(blank)'' |- | {{#invoke:Yesno|yesno|}} | {{yesno|}} | ''(blank)'' |- | {{#invoke:Yesno|yesno}} | {{yesno}} | ''(blank)'' |- | {{#invoke:Yesno|yesno|¬}} | {{yesno|¬}} | ''(blank)'' |- | {{#invoke:Yesno|yesno|purplemonkeydishwasher}} | {{yesno|purplemonkeydishwasher}} | yes |- | {{#invoke:Yesno|yesno|yes|yes=bacon}} | {{yesno|yes|yes=bacon}} | bacon |- | {{#invoke:Yesno|yesno|no|no=ham}} | {{yesno|no|no=ham}} | ham |- | {{#invoke:Yesno|yesno|blank= eggs}} | {{yesno|blank= eggs}} | |- | {{#invoke:Yesno|yesno|no=ham}} | {{yesno|no=ham}} | |- | {{#invoke:Yesno|yesno|blank= eggs|no=ham}} | {{yesno|blank= eggs|no=ham}} | |- | {{#invoke:Yesno|yesno|¬|¬=sausage}} | {{yesno|¬|¬=sausage}} | sausage |- | {{#invoke:Yesno|yesno|purplemonkeydishwasher|def=cup-of-tea}} | {{yesno|purplemonkeydishwasher|def=cup-of-tea}} | cup-of-tea |- | {{#invoke:Yesno|yesno|purplemonkeydishwasher|yes=bacon}} | {{yesno|purplemonkeydishwasher|yes=bacon}} | bacon |- | {{#invoke:Yesno|yesno|purplemonkeydishwasher|def=cup-of-tea|yes=bacon}} | {{yesno|purplemonkeydishwasher|def=cup-of-tea|yes=bacon}} | cup-of-tea |- | {{#invoke:Yesno|yesno|yes|yes=no|no=yes}} | {{yesno|yes|yes=no|no=yes}} | no |- | {{#invoke:Yesno|yesno|no|yes=no|no=yes}} | {{yesno|no|yes=no|no=yes}} | yes |- | {{#invoke:Yesno|yesno| no |no=no}} | {{yesno| no |no=no}} | no |}
- Note: Pre tags added to suppress script errors. — Mr. Stradivarius ♪ talk ♪ 14:25, 20 September 2013 (UTC)
As you can see, the template does not behave exactly as its documentation claims it does. I was not sure which to regard as authoritative: the ideal or actual implementation. I ultimately went with the former. Removing and not any
from the Lua code will make the module behave like exactly like the template.
--Ori.livneh (talk) 10:46, 28 February 2013 (UTC)
- Just needs to handle spaces in the params better. -- WOSlinker (talk) 11:41, 2 March 2013 (UTC)
- Thanks. Fixed. I moved your test case to the table above. --Ori.livneh (talk) 05:58, 3 March 2013 (UTC)
The documentation is wrong. The "egg" example assumes thet the input value is blank. But in the code examples the input parameter is omitted. Compare:
- {{yesno|blank= eggs|no=ham}} →
- {{yesno||blank= eggs|no=ham}} → eggs
This is what is actually documented:
- {{yesno|blank= eggs|no=ham|¬=bread}} → bread
Why?
{{yesno}} is quite simple, so I'm not sure if there is a point in replacing it with functionally equivalent Lua. There are many cases where Lua can be much faster and easier to read, but I'm not sure that is the case here. In fact, because of the slight overhead with #invoke, simple parser functions can actually be slightly faster than the equivalent Lua. I haven't tested that here, but I wouldn't be surprised if there is no performance advantage in a case like this. Seems like a strange template to target for Lua conversion. Dragons flight (talk) 14:57, 12 March 2013 (UTC)
See also
- {{[[Module:{{{1}}}|#invoke:{{{1}}}]]|function}}
test failed
Template:Resolved One fail found in unit test: value "1= ¬ " (with whitespace). Reason:whitespace not removed before this check. Possible solution; treat '¬' as a character, separate from nil. (if val == nil or val == '¬' then ...). -DePiep (talk) 11:54, 23 March 2013 (UTC)
- Another fail: input value="00". See Module talk:Yesno/testcases. -DePiep (talk) 12:56, 23 March 2013 (UTC)
- also fails when 1=0.0
- Suggestion: change
val = args[1]
intoval = tostring(args[1])
. To prevent treating "000" as number. -DePiep (talk) 14:09, 23 March 2013 (UTC)
Solved. Module is changed, although the numeric issue different from my (incorrect) suggestion. -DePiep (talk) 14:19, 23 March 2013 (UTC)
- Thanks for putting the test cases up. I learned something new about ParserFunctions. :) Still seems to be slower than the old template version though. — Mr. Stradivarius ♪ talk ♪ 14:38, 23 March 2013 (UTC)
Null?
The code now says no = "<!-- null -->"
. But a "" (nullstring) is not the same as ASCII NULL (0x0000). Also I see no use for adding wiki comment to code this way. -DePiep (talk) 17:47, 23 March 2013 (UTC)
- Yes, I agree that it doesn't really make sense. It's just in there to be 100% backwards-compatible with the current template. Those html comments should really have been removed from {{yesno}} when it was made subst-able, which would have prevented us from having to second-guess whether they actually affect the output of any substitutions in any meaningful way. I suppose it's possible to download a database dump and to run a search on it to find out, but that's probably a bit much for my poor ailing laptop. Or we could just remove the comments and hope nothing breaks - I'm fairly sure that no-one would have written any template code that purposefully used them. There's no way to be sure that there is no code that was inadvertently written to be dependent on the error, though, and that worries me. — Mr. Stradivarius ♪ talk ♪ 18:24, 23 March 2013 (UTC)
Rewrite
I've rewritten this as a pure Lua function. The new version is a lot simpler, and is also designed to work with Lua data types such as booleans, tables, and functions. Dragons flight's criticism above is well-founded, and giving up on the idea of replacing {{yesno}} seemed like the best answer. The new version should hopefully retain the basics of {{yesno}} while playing well with Lua, and allow meta-modules that deal with boolean-style wikitext input to be consistent with each other. (In other words, users won't have to remember whether it was "category=yes" or "category=true" - it should Just WorkTM.) — Mr. Stradivarius ♪ talk ♪ 14:37, 20 September 2013 (UTC)
All testcases failed
is there some issue with the module, all tests on the Module talk:Yesno/testcases has failed. --Jarekt (talk) 16:37, 20 December 2013 (UTC)
Protected edit request on 24 February 2014
Template:Edit protected the information is deceptive
please delete 2600:1013:B018:986F:4493:7A2A:52E2:103A (talk) 04:21, 24 February 2014 (UTC)
- File:Red question icon with gradient background.svg Not done: please be more specific about what needs to be changed. Note that this is the talk page for Module:Yesno and there is no information here. What information on which page do you think is deceptive? — {{U|Technical 13}} (t • e • c) 04:27, 24 February 2014 (UTC)
New version
I've put a new version of this module in the sandbox. The new version uses the native Lua string.lower function instead of the Scribunto mw.ustring.lower function. According to my tests it is about 25x faster this way. Would anyone object to me updating the module? — Mr. Stradivarius ♪ talk ♪ 15:22, 7 April 2014 (UTC)
- I see no issue with it. Jackmcbarn (talk) 18:57, 7 April 2014 (UTC)
- The new version is live as of the 18th. — Mr. Stradivarius ♪ talk ♪ 12:33, 22 April 2014 (UTC)
Doc questions (blank string true/false)
- In the documentation, I changed the "nil" example into singular. Or are there are other forms of nil covered and to be documented? (uppercase?, a non-initialised variable?).
- The last paragraph is about the
''
value (blank string). It says:
- Although the blank string usually evaluates to false in wikitext, it evaluates to true in Lua. Is this correct here?
- According to this same documentation, it is treated as "not a boolean". It says it returns the default (parameter) value, not the 'true' value. That is: not recognised as a boolean, iic. And elsewhere the doc says "
yesno('')
returns nil". (I did not test any). -DePiep (talk) 09:06, 8 April 2014 (UTC)
- On nil: there is only one kind of nil. However, there may be many variables in any given module whose value may be nil, hence "nil values". There is no "uppercase nil", and in Lua there is no such thing as a non-initialised variable, as variables are initialised when they are first used. On the blank string: saying that it "evaluates to true" is talking about when it is used in if/then statements or with the
and
andor
operators. For example, the following code will return true:
- On nil: there is only one kind of nil. However, there may be many variables in any given module whose value may be nil, hence "nil values". There is no "uppercase nil", and in Lua there is no such thing as a non-initialised variable, as variables are initialised when they are first used. On the blank string: saying that it "evaluates to true" is talking about when it is used in if/then statements or with the
if '' then
return true
else
return false
end
- Does that clear things up? — Mr. Stradivarius ♪ talk ♪ 09:26, 8 April 2014 (UTC)
- Does it clear things up? Don't know. Documentation did not change. -DePiep (talk) 12:10, 8 April 2014 (UTC)
- I mean, do you understand it now? — Mr. Stradivarius ♪ talk ♪ 12:34, 8 April 2014 (UTC)
- Does it clear things up? Don't know. Documentation did not change. -DePiep (talk) 12:10, 8 April 2014 (UTC)
- Does that clear things up? — Mr. Stradivarius ♪ talk ♪ 09:26, 8 April 2014 (UTC)