removeEveryEndpoint gone in 1.3.16 but still referenced in docs

[GoogleCodeExporter]

I just updated to 1.3.16 from .14 and had code using 
jsPlumb.removeEveryEndpoint(). That method seems to be gone in 1.3.16, even 
though it is still reference in the documentation 
(http://jsplumb.org/doc/usage.html).

The similarly-named jsPlumb.removeAllEndpoints() doesn't do the same thing, 
although I at first thought it would. I've switched to using .reset(), but it 
seems to remove my binding to jsPlumb's 'click' event, unfortunately. Is there 
another alternative to removeEveryEndpoint that I should use?

Also, where is the list of changes from .14 to .15 archived? Do I need to look 
at the commit history in github?

Thanks!
Pat

Original issue reported on code.google.com by pckuj...@gmail.com on 6 Dec 2012 at 2:05

[GoogleCodeExporter]

changes are in the changelog:

https://github.com/sporritt/jsPlumb/blob/master/changelog.txt

* 1.3.15

        BACKWARDS COMPATIBILITY

        - 'removeEveryEndpoint' method removed from jsPlumb. use 'deleteEveryEndpoint'.
        - 'removeEndpoint' method removed from jsPlumb. use 'deleteEndpoint'.

Original comment by simon.po...@gmail.com on 6 Dec 2012 at 2:12

• Added labels: Type-Other
• Removed labels: Type-Defect

[GoogleCodeExporter]

updated docs.

Original comment by simon.po...@gmail.com on 6 Dec 2012 at 2:17

• Changed state: Done
• Added labels: 1.4.0

[GoogleCodeExporter]

Thanks for the links! The docs still have two references to 
removeEveryEndpoint, though .

Original comment by pckuj...@gmail.com on 6 Dec 2012 at 3:22

[GoogleCodeExporter]

the docs dont get updated until the new release goes out.  so this is fixed in 
dev but not on the site.

Original comment by simon.po...@gmail.com on 6 Dec 2012 at 3:23

[GoogleCodeExporter]

I see. Since it was useful to me, might I suggest adding a link to the github 
changelog on the docs page after the summary of the latest changes? I'm sure 
others would find it useful too.
Thanks!
Pat

Original comment by pckuj...@gmail.com on 6 Dec 2012 at 5:15

[GoogleCodeExporter]

sure, why not.  i've done that.

but of course you wont see it on the site until 1.4.0 is released....

Original comment by simon.po...@gmail.com on 6 Dec 2012 at 7:44