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] Improve Navigation and Presentation of Large MQTT Messages #1878

Open
ppfeiler opened this issue Feb 26, 2025 · 0 comments
Open

[Feature] Improve Navigation and Presentation of Large MQTT Messages #1878

ppfeiler opened this issue Feb 26, 2025 · 0 comments
Labels
feature This pr is a feature

Comments

@ppfeiler
Copy link

Motivation

During the testing of our MQTT implementation, I frequently encounter extremely large messages, often JSON-structured, with over 1000 lines each. Navigating through these messages is cumbersome due to the need for extensive scrolling. To enhance productivity and efficiency, the following features would be highly beneficial:

  • Display the message timestamp prominently at the beginning of each message to facilitate quick identification and context gathering.
  • Implement a mechanism to jump easily between messages, minimizing navigation time and frustration.
  • Introduce the ability to collapse and expand lengthy messages to improve readability and minimize visual clutter.

These enhancements would significantly streamline message analysis and improve the overall user experience for developers working with large datasets in MQTT.

Detailed design

Example for the mechanism to jump easily between messages:

  • Image
  • Image

Example for the ability to collapse and expand lengthy messages:

  • Image
@ppfeiler ppfeiler added the feature This pr is a feature label Feb 26, 2025
@github-project-automation github-project-automation bot moved this to Backlog in MQTTX Feb 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature This pr is a feature
Projects
Status: Backlog
Development

No branches or pull requests

1 participant