Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add sparkplug b encoder for publishing #655

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

ferm10n
Copy link

@ferm10n ferm10n commented Jun 7, 2022

Continuing off the work of #629 and #582, this PR adds the ability to publish sparkplug B payloads.

I'm looking for input on the method used for determining when to encode (checking if the topic is sparkplug like via regex) and how error handling should be done when the format is incorrect (currently a no-op)

@ferm10n ferm10n force-pushed the encoding-sparkplug branch from 3dc2019 to d724dbc Compare June 7, 2022 15:32
@ferm10n
Copy link
Author

ferm10n commented Jul 21, 2022

Also I should mention that I fixed the linting step in CI. I hope that was ok. Doing so exposed a warning in an unrelated file, that I'm not sure how to address.

@bj00rn
Copy link
Collaborator

bj00rn commented May 2, 2024

@ferm10n Can you rebase this, and hopefully we can get it merged?

@ferm10n ferm10n force-pushed the encoding-sparkplug branch from adae442 to 4df2577 Compare May 3, 2024 16:49
@ferm10n ferm10n force-pushed the encoding-sparkplug branch from e826405 to 58c3c9e Compare May 3, 2024 18:34
@ferm10n
Copy link
Author

ferm10n commented May 3, 2024

@bj00rn ready for review.

I did have a question about https://github.com/thomasnordquist/MQTT-Explorer/pull/655/files#diff-5255694efe3f339a40eef198ab371f5c050b53e65146bb32aa2dbb2427646beaR39, did you have a preference on how to handle an error when trying to encode a sparkplug payload (for example when the user provides a payload that cannot be sparkplug encoded)

@bj00rn
Copy link
Collaborator

bj00rn commented May 16, 2024

@ferm10n thanks for this, I think we have to sort out decoding/encoding logic before looking into this there are a few issues/pr around this ATM

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