Closed Enngage closed 6 years ago
Any chance you can fix this?
@Enngage I will look into this as soon as I can, been busy in my job ;)
@Enngage please try 0.9.6
and report back if there's a behavior change with the strict null changes ;)
Awesome, thanks :) I just went on Vacation so I won't be able to check right now, but will as soon as I can.
On Mon, 23 Jul 2018 at 18:42, Mateo Tibaquirá notifications@github.com wrote:
@Enngage https://github.com/Enngage please try 0.9.6 and report back if there's a behavior change with the strict null changes ;)
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/selvera/npm-datepicker/issues/13#issuecomment-407122920, or mute the thread https://github.com/notifications/unsubscribe-auth/AGzoR2BWZfWVcPjax4kgWUi1-9WytIu8ks5uJfzegaJpZM4VAoIk .
@Enngage this should be completely fixed on @coachcare/datepicker 0.9.9
Hi, another one :-)
Production build with with
ts.config
option:"strictNullChecks": true
and Angular specific:
Fails with:
ERROR in node_modules\@coachcare\datepicker\coachcare-datepicker.d.ts.MatYearsView.html(3,3): : Object is possibly 'null'.