Feature Request: Allow esp_at_get_para_as_str() to parse unquoted string parameters

[rohitsam]

Is your feature request related to a problem?

currently, esp_at_get_para_as_str() in ESP-AT only supports parsing strings that are enclosed in double quotes (e.g., AT+MYCMD="Hello"\r\n).
If a parameter is passed without quotes (e.g., AT+MYCMD=Hello\r\n), it is not recognized as a valid string.

Is there a way to do this in the currrent version of esp-at

Describe the solution you'd like.

Update esp_at_get_para_as_str() to check for quotes, and if none are found, treat the token as an unquoted string.

Describe alternatives you've considered.

No response

Additional context.

No response

[ustccw]

Hi @rohitsam Thanks for your suggestion! I see you're requesting the format to be like this:

AT+MYCMD=Hello\r\n

Currently, the format we use includes the quotes:

AT+MYCMD="Hello"\r\n

This is because the quotes are part of the standard syntax for string values in AT commands, and removing them might cause issues with how the command is parsed or interpreted in certain situations. For example, receiving AT+MYCMD=1234\r\n, without the quotes, it could cause confusion, especially if the value is numeric or looks like a command parameter, leading to unexpected behavior.

Could you let us know more about why you'd prefer it without the quotes?