Expose `stopExpiringSessions` so that Mocha 4 can exit gracefully about connect-session-sequelize

[mweibel]

Ok, I see. Please open a PR with your proposed change and I'll gladly review it.

[mweibel]

That sounds reasonable. However: I had the same issue recently with the tests in this very module:
cbaa4b0

How about you'd also just give an expiration interval of -1 when in the tests?

[glebec]

@mweibel, you could definitely do so, but then you are modifying the session store behavior for testing, rather than cleaning up resources after testing. On principle I prefer to keep tested code as close to production as is reasonable.

[mweibel]

True. Though my question is what would you like to change? stopExpiringSession is already a public API. I'd welcome a PR.

[glebec]

It’s publicly exposed but not documented, making it arguably an implementation detail rather than an API method. Explicitly documenting it as a feature would both aid in discovery and also signal that it is ok to use and will be tracked in SEMVER.