Scott Simpson

@isiahmeadows I didn't mean to suggest you didn't know these are breaking changes 😀

@Manidos great catch! You should PR that :)

I think it's worth asking: is a Promise _chain_ the more-common use case? > Considering how (not) often it is you want to request data and immediately re-render, it'd make...

> I thought nobody need this feature so source map was omitted. > Fix later... feel free to rise a PR. Hi there, is there any movement on this? I...

@gjmcn here (in your two commented-out examples, which are functionally identical) you have a pretty good example of an anti-pattern: you're directly mutating the nested properties of an object which...

This is almost certainly a keying issue — try passing a unique key to each div in your map, right next to style & onclick. https://mithril.js.org/keys.html

mmm. Try creating a unique id field for the actual source objects and just use that. Relying on array index is a footgun. Sent from my iPhoneOn Oct 8, 2023,...

@cmnstmntmn Thanks! What if I just exposed a "range" prop, with optional start/end? That way, disabling the past would be : ```js m(DatePicker, { range: { start: "now" } })...

@futurist One of the really big goals of this project was to eliminate the possibility of invalid dates, so user text input was purposefully excluded. If this issue is cited...