Skip to content

refactor: typed device topic id in tedge config#3864

Merged
albinsuresh merged 1 commit intothin-edge:mainfrom
albinsuresh:refactor/typed-device-topic-id-in-tedge-config
Nov 19, 2025
Merged

refactor: typed device topic id in tedge config#3864
albinsuresh merged 1 commit intothin-edge:mainfrom
albinsuresh:refactor/typed-device-topic-id-in-tedge-config

Conversation

@albinsuresh
Copy link
Copy Markdown
Contributor

@albinsuresh albinsuresh commented Nov 18, 2025

Proposed changes

Use typed device topic id in tedge config

Types of changes

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)
  • Documentation Update (if none of the other choices apply)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Paste Link to the issue


Checklist

  • I have read the CONTRIBUTING doc
  • I have signed the CLA (in all commits with git commit -s. You can activate automatic signing by running just prepare-dev once)
  • I ran just format as mentioned in CODING_GUIDELINES
  • I used just check as mentioned in CODING_GUIDELINES
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)

Further comments

serde = { workspace = true, features = ["rc"] }
strum = { workspace = true }
strum_macros = { workspace = true }
tedge_api = { workspace = true }
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hope this is fine.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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
Copy link
Copy Markdown

codecov bot commented Nov 18, 2025

@github-actions
Copy link
Copy Markdown
Contributor

Robot Results

✅ Passed ❌ Failed ⏭️ Skipped Total Pass % ⏱️ Duration
742 0 3 742 100 2h21m4.121199999s

Copy link
Copy Markdown
Contributor

@didier-wenzek didier-wenzek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved

serde = { workspace = true, features = ["rc"] }
strum = { workspace = true }
strum_macros = { workspace = true }
tedge_api = { workspace = true }
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@albinsuresh albinsuresh added this pull request to the merge queue Nov 19, 2025
Merged via the queue into thin-edge:main with commit 89777a8 Nov 19, 2025
34 checks passed
@albinsuresh albinsuresh deleted the refactor/typed-device-topic-id-in-tedge-config branch November 28, 2025 10:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants