refactor: typed device topic id in tedge config#3864
Conversation
| serde = { workspace = true, features = ["rc"] } | ||
| strum = { workspace = true } | ||
| strum_macros = { workspace = true } | ||
| tedge_api = { workspace = true } |
There was a problem hiding this comment.
Hope this is fine.
There was a problem hiding this comment.
This is not ideal, but okay. Somehow the issue is not new. tedge_config is already depending on mqtt_channel only to get some Topic and TopicFilter types. Also, tedge_api is a mix of global concepts such as EntityTopicId and mechanisms such as workflows. To fix that we would have to introduce a crate with the types used by all thin-edge components.
Codecov Report❌ Patch coverage is 📢 Thoughts on this report? Let us know! 🚀 New features to boost your workflow:
|
Robot Results
|
| serde = { workspace = true, features = ["rc"] } | ||
| strum = { workspace = true } | ||
| strum_macros = { workspace = true } | ||
| tedge_api = { workspace = true } |
There was a problem hiding this comment.
This is not ideal, but okay. Somehow the issue is not new. tedge_config is already depending on mqtt_channel only to get some Topic and TopicFilter types. Also, tedge_api is a mix of global concepts such as EntityTopicId and mechanisms such as workflows. To fix that we would have to introduce a crate with the types used by all thin-edge components.
Proposed changes
Use typed device topic id in tedge config
Types of changes
Paste Link to the issue
Checklist
just prepare-devonce)just formatas mentioned in CODING_GUIDELINESjust checkas mentioned in CODING_GUIDELINESFurther comments