Hi Niels,
Unfortunately this is part of a public facing API, so it's a bit tough to
change without breaking a bunch of dependent code. So, I think despite the
annoying spelling mistake, it's not worth the pain to fix because of the API
breakage :(
If you find other spelling mistakes that are part
Is there really much harm in deprecating the incorrect spelling and providing a
correct spelling equivalent?
--Chris
On Dec 26, 2010, at 6:19 PM, Todd Lipcon wrote:
> Hi Niels,
>
> Unfortunately this is part of a public facing API, so it's a bit tough to
> change without breaking a bunch of d
