RE: APIs that have boolean arguments defaulting to true from Domenic Denicola on 2013-11-11 (public-script-coord@w3.org from October to December 2013)

From: Domenic Denicola <domenic@domenicdenicola.com>
Date: Mon, 11 Nov 2013 20:18:45 +0000
To: "Mark S. Miller" <erights@google.com>, Boris Zbarsky <bzbarsky@mit.edu>
CC: "public-script-coord@w3.org" <public-script-coord@w3.org>
Message-ID: <ad062c77fe544e32a794e65fa3313a36@BN1PR05MB325.namprd05.prod.outlook.com>

My impression was that boolean arguments in general should be avoided. "The Boolean Trap", as it's called:

http://ariya.ofilabs.com/2011/08/hall-of-api-shame-boolean-trap.html

https://www.google.com/search?q=boolean+trap

For example, `node.clone({ shallow: true })` or `node.clone({ deep: true })` seems much better than `node.clone(true)` or `node.clone(false)`.

Received on Monday, 11 November 2013 20:19:27 UTC