You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 7, 2020. It is now read-only.
isLinked(channel) throws an exception when the channel in argument does not exist for the thing.
When a binding is enhanced with a new channel and a user updates to this new binding version, a use of isLinked for the new channel will lead to an exception until the user removes his thing and create another one.
I am asking myself if the exception should not be catched by isLinked and if the channel does not exist then returns false ?
Another option would be to be modify every binding using isLinked to catch the exception. Lot of work.
It leads to another consideration: would it be possible to automlatically add the new channels to old things.
The text was updated successfully, but these errors were encountered:
IMHO the last option would be best. The OH2 Astro binding had the Same problem. As long as only one or two things need to be updated, manually doing so is ok, but imagine a OneWire binding where you need to configure each sensor again.
isLinked(channel) throws an exception when the channel in argument does not exist for the thing.
When a binding is enhanced with a new channel and a user updates to this new binding version, a use of isLinked for the new channel will lead to an exception until the user removes his thing and create another one.
I am asking myself if the exception should not be catched by isLinked and if the channel does not exist then returns false ?
Another option would be to be modify every binding using isLinked to catch the exception. Lot of work.
It leads to another consideration: would it be possible to automlatically add the new channels to old things.
The text was updated successfully, but these errors were encountered: