Andrew Plummer

Ahh ok this is making more sense now. Also ignore my above comment, I was misunderstanding something. However it leads me to another question. For the method `fromQueryString`, there is...

Oh believe me, I've been over that document many times now....

Ok, I fixed the issues raised in the comments: 1. `isArray`, `isString`, etc. accept `any` instead of `Object`. 2. Callback functions like `mapFn` are now passed generics. The previous definitions...

Please have a look. I will also have a more thorough look at how generics are being used in each method later. However I think these should probably be ok...

Another issue raised with definitions... it seems that this won't work: ```typescript import SugarDate from 'sugar/date' ``` Having a look at how lodash does it, there seems to be a...

Update: It seems that `export default Sugar` is incompatible with node modules, so it will need to be required with `import * as Sugar from 'sugar'` or `import Sugar =...

That is correct, even though a `Sugar.RegExp` instance (aka a "chainable") has native methods mapped onto it, they are not the exact same instance methods as on native `RegExp`, but...

So this has taken some time to look into... there are a couple issues happening here at the same time... If you want the short version, I'm not sure why...

Hi... give me a bit and I will look into this. Thanks for helping out here.

Yikes... ok thank you! As a workaround you can mess with the locale file and try moving certain formats from `timeParse` into `parse` and/or simply removing the `timeMarker` prop...