As mentioned in the gist, and FWIW, -1 here. `/^true$/i.test(str)` works since ever for the specified use case
`Boolean.parseBoolean(1)` that returns `false` is a footgun. Either we talk about a better definition of truthy-like values, or having a public spec about just string type and `true` as value looks like the solution for 1% of use cases that's also already covered by `JSON.parse` Regards On Mon, Mar 20, 2017 at 7:07 PM, James Treworgy <[email protected]> wrote: > I'd say there's no clear model for consistenty, e.g. JSON.parse. One could > argue that the template is that anything which has only one way to parse is > to use `parse`. Numbers have more than one way (`parseInt`, `parseFloat`) > > > On Mon, Mar 20, 2017 at 3:04 PM, Dmitry Soshnikov < > [email protected]> wrote: > >> On Mon, Mar 20, 2017 at 11:57 AM, T.J. Crowder < >> [email protected]> wrote: >> >>> Any reason for not just using `Boolean.parse`? (Rather than repeating >>> `Boolean` in the function name?) >>> >>>> >>>> >> Just a copy-paste from Java, similarly was done with `parseInt` taken >> from Java. But just `parse` probably would work too. For consistency and >> predictability `parseBoolean` is probably better now. >> >> Dmitry >> >> _______________________________________________ >> es-discuss mailing list >> [email protected] >> https://mail.mozilla.org/listinfo/es-discuss >> >> > > _______________________________________________ > es-discuss mailing list > [email protected] > https://mail.mozilla.org/listinfo/es-discuss > >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
