William Warby

The related getter and setter for the `value` property are also declared as `string`- these should also be changed to `any`.

I've submitted a pull request for this: https://github.com/valor-software/ngx-bootstrap/pull/6446 - hope I've done it correctly, it's my first for this repo

@mikerhyssmith, any chance you could describe how to use this feature? I'm in the process of migrating from Angular 1 with angular-google-analytics to Angular 5 with Angulartics so not yet...

I've just hit exactly the same problem. It seems like SqlMapper handles enums differently than every other type and tries to map them with Enum.Parse even if a custom type...

Urgh. I knew Dapper was optimised for performance but I didn't realise it literally emitted IL op codes to do value conversions. No chance I'm ever going to get to...

Any update on this? I could be up for contributing as I'd like to start using v4 lists in my own project.

I put this aside for a while due to other priorities but I'm gonna need to start using these APIs soon, so I need to either add support for this...

I've just had a closer look at the documentation and it seems everything I need is actually available in the v3 API - don't know why I didn't notice that...

This does seem like intentional behaviour - it's documented in the README, although I'd say it's highly undesirable, as you're left with the choice of giving the user no starting...

I've also run into this one when updating from Node 12.7 to 13.9, but I found that going back as far as 12.16 didn't help - I had to go...