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
When migrating from OH 2.5.x to 3.0 I ended up having items refer to non-existing things (uploaded .items file in UI, referring to onewire things with an old unique ID). When editing such an item in the UI, this is what you get:
As you can see in the network tab, the REST API rightfully responds with a 404 for the old thing that does not exist anymore. But the UI does not handle this case gracefully, showing not any channel link.
Expected behavior
The UI should display
the broken channel link, with a way to remove that
the two healthy links (see successful requests below the 404)
Steps to reproduce
As described above, uploading an .items file with a broken channel definition should reproduce this error.
Display links which are invalid (for instance, missing
thing or channel) and offer the option to remove them.
Cleanups.
Fixesopenhab#709.
Signed-off-by: Yannick Schaus <github@schaus.net>
Display links which are invalid (for instance, missing
thing or channel) and offer the option to remove them.
Cleanups.
Fixes#709.
Signed-off-by: Yannick Schaus <github@schaus.net>
Display links which are invalid (for instance, missing
thing or channel) and offer the option to remove them.
Cleanups.
Fixes#709.
Signed-off-by: Yannick Schaus <github@schaus.net>
The problem
When migrating from OH 2.5.x to 3.0 I ended up having items refer to non-existing things (uploaded .items file in UI, referring to
onewire
things with an old unique ID). When editing such an item in the UI, this is what you get:As you can see in the network tab, the REST API rightfully responds with a 404 for the old thing that does not exist anymore. But the UI does not handle this case gracefully, showing not any channel link.
Expected behavior
The UI should display
Steps to reproduce
As described above, uploading an .items file with a broken channel definition should reproduce this error.
Your environment
Browser network traffic
See above.
The text was updated successfully, but these errors were encountered: