@constructor vs @factory

[nathancahill]

Most leaflet classes have a factory function (@factory) that outputs to the Creation section of the class. Can we add @constructor functions there too? Some classes only have constructors, so their docs are missing.

[nathancahill]

This is what I have in mind, for something like L.Draggable that only has a @constructor:

And potentially for classes that use both @factory and @constructor?

[mourner]

I think we eventually want to get rid of all public constructors and have only one way to create instances.

[nathancahill]

Makes sense. Would you entertain a pull request that adds factory functions for the couple of classes that are missing them?

[mourner]

Yes, we could do that. As far as I remember, I didn't add factories to some classes like L.Draggable because I wasn't even sure they should be exposed publicly in the API as opposed to internal use only. It increases complexity while having no use for most users.

[IvanSanchez]

I've added the constructor (and as a bonus, the destructor) documentables to , with a basic template.

How we document Leaflet is outside of the scope of this bug, though. I do agree with @mourner in that we should only expose (through the docs) the factories we want, and no constructors at all.