Eric Loren
Eric Loren
[PR here](https://github.com/reasonml/esy/pull/23) since history doesn't track across repos.
Sure thing. The datepicker code takes the position (not mine, inherited from the old days) that all model data ought to be encapsulated (presumably to avoid causing too many version...
Re-fixed in #65.
Issue is reopened; the solution unfortunately necessitated removing the state var `inputText`, which we can't actually do without.
Nice idea! Sometimes I say to myself, "Well, if we add enough settings the user may as well just render their own view!", but since this isn't complicated I don't...
Merged! #80 and #81 have recent activity on them, so I was thinking I might try to bundle any resulting work together as a single release (since #80 is likely...
Yes indeed. It looks like the problem could be that when submitting date text, a failure to parse passes through `Result.withDefault NoChange`, leaving the text intact. If we were just...
Yeah, a more opinionated lib could decide to add messaging to indicate invalidity of text, but it doesn't take _that_ long to type a date, so I guess blowing it...
This is not a known bug but I can see what's happening. Thanks for the report! For anyone who's interested, the problem is that the picker only processes `blur` events...
I believe it's just that it used to return commands that were used to, among other things, need/retrieve the current date. It's probably cruft that just wasn't removed along with...