-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove lib.connection #410
Comments
Todo: check plugins before next release |
currently using lib.connections:
|
LOGO might be still in use by @ivande, I have no idea about comfoair |
Maybe you should ask in the forum and on gitter, if the two plugins are still in use (and if someone is maintaining them). |
Checking again, I already migrated the sv_websocket is one building its own network server from lib.connections, but as far as I recall this is deprecated... So lib.connection could be removed at one of the next releases. The deprecation warning is already implemented for those using lib.connection in private plugins. |
Sc_websocket ist deprecated and will be retired in v1.10. There is no need to update it. It has been replaced by the websocket module. |
SmartHomeNG v1.9.4 has been released |
After transitioning active code in core and plugins to lib.network, the lib.connection ist obsolete (concerning code checked in on GitHub / smarthomeNG) following issue 399 @plugins
One consideration before finally removing lib.connection should be a way to warn users incorporation lib.connection in private plugins.
Options might be
Removal should be planned earliest for 1.10, latest for 2.0, IMHO.
The text was updated successfully, but these errors were encountered: