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
Currently, this is our atclient_monitor_response_type enum:
enumatclient_monitor_response_type {
// the following 4 enums help indicate what type of message was received from the monitor connection and which field// of the union to accessATCLIENT_MONITOR_MESSAGE_TYPE_NONE,
ATCLIENT_MONITOR_MESSAGE_TYPE_NOTIFICATION, // indicates caller to access `notification` from the unionATCLIENT_MONITOR_MESSAGE_TYPE_DATA_RESPONSE, // indicates caller to access `data_response` from the unionATCLIENT_MONITOR_MESSAGE_TYPE_ERROR_RESPONSE, // indicates caller to access `error_response` from the union// the following 3 enums help indicate what type of error occurred when reading from the monitor connection, you will// expect one of these enums along with a non-zero return value from atclient_monitor_readATCLIENT_MONITOR_ERROR_READ, // could be a read timeout or some other error, indicates the caller to access// `error_read` from the unionATCLIENT_MONITOR_ERROR_PARSE_NOTIFICATION,
ATCLIENT_MONITOR_ERROR_DECRYPT_NOTIFICATION,
};
I would like to propose that it be changed to this instead:
Currently, this is our
atclient_monitor_response_type
enum:I would like to propose that it be changed to this instead:
Reason for this change is
ATCLIENT_MONITOR_RESPONSE_
as the prefix.The text was updated successfully, but these errors were encountered: