Jon Koops
Jon Koops
Hmmmm, yeah I get the confusion. I meant to say that we would want to be able to use ES2015+ syntax, not necessarily that we're landing standardized classes in 2.0....
Awesome, I went ahead and branched off the [`v1`](https://github.com/Leaflet/Leaflet/tree/v1) branch so we can start merging breaking changes into `main`. Do we want to add a notice to the README that...
@mourner are you updating the docs, or would you like me to take a swing at it?
I've created a label to keep track of breaking changes like these.
@Falke-Design do we want to keep this in the 1.9 milestone or can we move this forward? I'd like to start working on a release.
In regards to TypeScript support, instead of adopting it for the source, it could also be supported by embedding the type definitions to the library itself in the form of...
> Not to be mean, but really, TS has become the bully on the playground. It solves genuine problems that people experience, but if it's a good fit for this...
@mourner @IvanSanchez Can I get your opinions on this? As a TypeScript user like many out there it would be hugely beneficial for us to have the type definitions out...
> Note that "Leaflet types" are maintained by completely different people. As one of the contributors to the types package for Leaflet I am more than willing to put that...
> Perhaps TS would suggest the best approach? One that we could all use, TS users or not? In this regard TypeScript has the same constraints, as it is compiled...