Hello developer community,
this is one of a few Ideas I like the AC to consider for OH3.
The REST interface provides multiple endpoints. Unfortunately those feel like totally different subsystems with own data structures each. To ease the use I propose the following breaking changes:
- Unify IDs: At the moment we have
idfor extensions and
uidfor rules. Shorten this list to
uid(those two are semantically different, so just id is not enough).
- Unify Status reports: At the moment Things and Rules support an extended status report. But both endpoints do it differently.
- Unify config handling: Some endpoints like the one for Things include configuration while other endpoints like the service+binding ones have a separate
/configendpoint to retrieve configuration values.
- Item handling requires a lot of knowledge in clients. Add REST endpoints to allow for requesting all possible Item types and item group functions. The client should not have a static list that runs out of sync at some point.