Release of v2.1.0

[jimmynotjim]

v2.1 adds support for public methods, a new destroy method, custom callbacks for init, render and destroy, and small bugfixes.

• Reorganized core to allow for new public methods
• Added destroy method to core to allow for breaking down the plugin and it's dom changes
• Added the option to add callback functions to init, render and destroy
• Squashed a bug when wrapping sub-sections in their div
• Updated core init in test for easier reuse
• Fixed Grunt test:browser task to only run in the browser
• Added destroy tests to core module and a new module for the callbacks

[michael-benin-CN]

Thank you for maintaining this project. Does this fix the issue if the DOM updates the scrollNav plugin also resets?

[jimmynotjim]

@michael-benin-CN Nope, updating the DOM is going to be on you. I don't want to add complexity or additional file size by having to monitor the target elements content. When you script in the changes to update the DOM, you should destroy scrollNav just prior, and re-init after the DOM change. The custom callback functions and the new destroy method should provide you plenty of options for doing this.