[Feature] Enhance JSON syntax error messages

[ysfscream]

Currently, in MQTTX, when the selected data format for receipt is JSON, but the received data is not in JSON format, numerous error pop-ups are triggered. This can lead to a frustrating user experience as it lacks optimization. There is a need for more specific error messages for each incorrect message, including during script processing, instead of multiple pop-up alerts.

Detailed Design

To resolve this issue, I propose improving JSON syntax error messages in MQTTX. We can handle syntax errors more gracefully by providing detailed error messages for each incorrect message directly in the message stream, instead of triggering multiple pop-up alerts.

We can add a dedicated error-handling mechanism that will:

• Check if the received message follows the JSON format if JSON is selected as the data format.
• Display an error message directly within the message stream, below script processing prompts, instead of a pop-up, to avoid style conflicts.
• The error message should specify the exact issue with the message's syntax, with a message similar to: "Used JSON format, and syntax error: xxx".

With these modifications, users can directly view the specific error information in the message stream without going through pop-up alerts. This not only lowers the usage difficulty for the user but also makes viewing error information more intuitive.

Alternatives

An alternative solution could be to ignore non-JSON formatted messages when JSON is selected as the data format. However, this could lead to confusion and missed data for the user. Another alternative is to keep the current system with multiple pop-ups, but as stated, this could lead to a frustrating user experience.

More detail (optional)

This feature would require a modification in the way MQTTX processes incoming messages and how it handles syntax errors. A new error-handling mechanism would need to be developed to check the syntax of incoming messages and provide detailed error messages directly in the message stream.

This feature aims to enhance the user experience by providing more specific and less intrusive error messages, thus making MQTTX more user-friendly and efficient.