You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the current version of MQTTX, when users select JSON as the data format, there is no distinct visual cue if the data in the messages is in JSON format. This can make it difficult for users to quickly and accurately locate JSON data when viewing large amounts. Users might feel inconvenienced by the inability to quickly identify JSON data.
Detailed Design
To resolve this issue, I propose supporting JSON highlighting for messages in MQTTX. We can add a code block or other types of highlighting for each message in JSON format. The specific implementation is as follows:
If the received message is in JSON format, it will be highlighted when displayed.
The highlighting could be placing the message in a code block or using other highlighting effects.
This highlighting effect should allow users to instantly recognize that the message is in JSON format.
Alternatives
One possible alternative is to add a tag next to the message indicating it's in JSON format. However, this might not be as intuitive and obvious as highlighting. Another alternative is to ignore this feature, which could make it difficult for users to quickly and accurately locate JSON data when viewing large amounts of data.
More Detail (optional)
Implementing this feature would require changes to how MQTTX processes and displays messages. A new feature needs to be developed to check if the received messages are in JSON format and to provide a highlighting effect for messages in JSON format.
This feature aims to enhance the user experience by highlighting messages in JSON format, enabling users to quickly and accurately identify JSON data.
The text was updated successfully, but these errors were encountered:
Motivation
In the current version of MQTTX, when users select JSON as the data format, there is no distinct visual cue if the data in the messages is in JSON format. This can make it difficult for users to quickly and accurately locate JSON data when viewing large amounts. Users might feel inconvenienced by the inability to quickly identify JSON data.
Detailed Design
To resolve this issue, I propose supporting JSON highlighting for messages in MQTTX. We can add a code block or other types of highlighting for each message in JSON format. The specific implementation is as follows:
Alternatives
One possible alternative is to add a tag next to the message indicating it's in JSON format. However, this might not be as intuitive and obvious as highlighting. Another alternative is to ignore this feature, which could make it difficult for users to quickly and accurately locate JSON data when viewing large amounts of data.
More Detail (optional)
Implementing this feature would require changes to how MQTTX processes and displays messages. A new feature needs to be developed to check if the received messages are in JSON format and to provide a highlighting effect for messages in JSON format.
This feature aims to enhance the user experience by highlighting messages in JSON format, enabling users to quickly and accurately identify JSON data.
The text was updated successfully, but these errors were encountered: