Brielle Harrison

Hmm, this seems to happen even with the most basic of schemas. Even if `schema A` and `schema B` are incredibly basic, local and neither are linked, the issue will...

Can you provide a working example?

Pull request and unit tests submitted. https://github.com/alexei/sprintf.js/pull/156

`typeof` and `Object.prototype.toString.call` are two very different things. They will also return different values for the same objects.

Thanks for that. Missed %T by the way. Nonetheless, you do not want to change the case because it prevents type.name comparisons. The way I see it there are three...

If you do, please allow functions and classes to be converted to type rather than being executed. There are real uses for that scenario. Especially when in conjunction with classes...

Yup. Again I defer to your choice. With the ability to use Symbols in code to specify custom return values for Object.prototype.toString.(call|apply), I have seen usage for this pattern increase...

I modified the files in the extension directory so they persist but yes, this is a usability issue I'd like to see corrected as well.

Any updates on this?