Currently, message-generator uses different key names to represent a message identifier:
When identifying a PoolMessages type with the keys "common_messages", "mining-messages", "job_negotiator_messages", or "template_distribution_messages", the identifier key is "id".
When identifying a PoolMessages type in the "frame_builders" key, the identifier key is "message_id".
When identifying a PoolMessages type in the "actions" key, the identifier key is "message_ids". This key's value is an array of message identifiers, which is why it is plural.
Need to use the same identifier names to avoid confusion. The chosen identifier name is "message_id" for a singular message identifier and "message_ids" for an array of message identifiers. Therefore, the only change should be:
When identifying a PoolMessages type with the keys "common_messages", "mining-messages", "job_negotiator_messages", or "template_distribution_messages", the identifier key SHOULD BE: "message_id".
Currently,
message-generator
uses different key names to represent a message identifier:PoolMessages
type with the keys"common_messages"
,"mining-messages"
,"job_negotiator_messages"
, or"template_distribution_messages"
, the identifier key is"id"
.PoolMessages
type in the"frame_builders"
key, the identifier key is"message_id"
.PoolMessages
type in the"actions"
key, the identifier key is"message_ids"
. This key's value is an array of message identifiers, which is why it is plural.Need to use the same identifier names to avoid confusion. The chosen identifier name is
"message_id"
for a singular message identifier and"message_ids"
for an array of message identifiers. Therefore, the only change should be:PoolMessages
type with the keys"common_messages"
,"mining-messages"
,"job_negotiator_messages"
, or"template_distribution_messages"
, the identifier key SHOULD BE:"message_id"
.