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

[Feature] Set a default message format during Subscription #1591

Open
V4G4X opened this issue Feb 26, 2024 · 2 comments
Open

[Feature] Set a default message format during Subscription #1591

V4G4X opened this issue Feb 26, 2024 · 2 comments
Assignees
Labels
desktop MQTTX Desktop enhancement New feature or request feature This pr is a feature web MQTTX Web
Milestone

Comments

@V4G4X
Copy link

V4G4X commented Feb 26, 2024

Motivation

I have set the format type to JSON whenever I use MQTTX, which I often forget, and I have to copy-paste my messages somewhere to format them.

Would LOVE for MQTTX to remember what format a device receives messages in and automatically format it.

Detailed design

I understand different devices work with different types, and even a single device often works with different topics that expect different formats.

It would be very helpful if we could configure this at the topic level while subscribing.
For example, an optional dropdown for format here:
image

Alternatives

The alternative is manually setting the format on starting MQTTX here:
image
And If you forget, your message doesn't look pretty and you have to copy-paste and do it yourself.

@V4G4X V4G4X added the feature This pr is a feature label Feb 26, 2024
@github-project-automation github-project-automation bot moved this to Backlog in MQTTX Feb 26, 2024
@V4G4X V4G4X changed the title [Feature] Set a default message format for received messages [Feature] Set a default message format during Subscription Feb 26, 2024
@ysfscream ysfscream self-assigned this Feb 27, 2024
@ysfscream ysfscream added web MQTTX Web desktop MQTTX Desktop enhancement New feature or request labels Feb 27, 2024
@ysfscream ysfscream added this to the v1.9.10 milestone Feb 27, 2024
@ysfscream
Copy link
Member

Thank you for sharing your motivation and the detailed design idea for enhancing MQTTX.

Implementing different formats for encoding/decoding messages for various topics within a single device presents significant design challenges. We're carefully considering this functionality and hope to find an innovative solution to accommodate such versatility without compromising the software's performance or user experience.

Thank you once again for your feedback. It's insights like yours that help us improve and evolve MQTTX better to meet the needs of our diverse user base.

@V4G4X
Copy link
Author

V4G4X commented Feb 27, 2024

Glad to hear that @ysfscream. Thanks a lot for taking this up!

@ysfscream ysfscream modified the milestones: v1.9.10, v1.10.1, v1.10.0 Apr 8, 2024
@ysfscream ysfscream modified the milestones: v1.10.0, v1.10.1 Jun 7, 2024
@ysfscream ysfscream modified the milestones: v1.10.1, v1.11.0 Jul 17, 2024
@ysfscream ysfscream modified the milestones: v1.11.0, v1.11.1 Oct 23, 2024
@ysfscream ysfscream modified the milestones: v1.11.1, v1.12.0 Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
desktop MQTTX Desktop enhancement New feature or request feature This pr is a feature web MQTTX Web
Projects
Status: Backlog
Development

No branches or pull requests

2 participants