3. Name not checked for undefined-ness but for falsy-ness

Name not checked for undefined-ness but for falsy-ness


  • This was only tested for createFlag, but might apply to other methods as well which ask for an optional name:

    When providing a falsy value (e.g. 0) as name, this parameter is ignored due to its falsy nature. The spec however states:

    If not defined, a random name will be generated.

    I'm aware that this is an edge case, as only 0 might make "kind of" sense as name (as opposed to "", null or false), but nonetheless it's an inconvenience.


  • Thanks, finally the annoying error is gone.

    Im doing a lot of java coding that's why i also assumed its "", null, false or even undefined.