Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mqtt5 GA API Review #575

Merged
merged 18 commits into from
Dec 4, 2023
Merged

Mqtt5 GA API Review #575

merged 18 commits into from
Dec 4, 2023

Conversation

xiazhvera
Copy link
Contributor

@xiazhvera xiazhvera commented Nov 28, 2023

Issue #, if available:

Description of changes:
Verified in aws/aws-iot-device-sdk-cpp-v2#659 that the change would not break current cpp v2.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@sfod
Copy link
Contributor

sfod commented Nov 29, 2023

There are some breaking changes (e.g., WithRetain() function removed or new enums being ambiguous). Maybe it'll be better to minimize breaking changes as much as possible?

@@ -450,7 +450,7 @@ static int s_AwsMqtt5CanaryOperationUnsubscribeBad(struct AwsMqtt5CanaryTestClie
unsubscription, [testClient](int, std::shared_ptr<Mqtt5::UnSubAckPacket> packet) {
if (packet == nullptr)
return;
if (packet->getReasonCodes()[0] == AWS_MQTT5_UARC_SUCCESS)
if (packet->getReasonCodes()[0] == UnSubAckReasonCode::AWS_MQTT5_UARC_SUCCESS)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This isn't what I had in mind for the enums. Did the original proposal not work?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As I'm creating the enum using the same value name in aws-c-mqtt (UnSubAckReasonCode:: AWS_MQTT5_UARC_SUCCESS v.s. aws_mqtt5_unsuback_reason_code::AWS_MQTT5_UARC_SUCCESS), the compiler would report an ambiguity error. I had to add the namespace to avoid the error.

One way to fix it is using a different enum value name in CPP. For example: UnSubAckReasonCode ::AWS_MQTT5_UARC_SUCCESS -> UnSubAckReasonCode::SUCCESS. In this case, we could still directly pass AWS_MQTT5_UARC_SUCCESS as the enum would be converted implicitly. However, it would break the user who was using UnSubAckReasonCode::AWS_MQTT5_UARC_SUCCESS.

I'm not sure if there is a better way to fix it.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That was what I intended:

enum class UnsubackReasonCode {
Success = AWS_MQTT5_UARC_SUCCESS,
... etc...
};

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. It seems that enum class would not be able to directly convert between int and enum value. Using enum class would definitely breaks the customer.

  2. If we removed AWS_MQTT5_UARC_SUCCESS and rename it to Success, then it would break the customer if they already use the enum with the namespace like following pattern:

UnSubAckReasonCode reasonCode = UnSubAckReasonCode::AWS_MQTT5_UARC_SUCCESS

Copy link
Contributor

@bretambrose bretambrose Nov 29, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You could double the entries with the palatable names, but I'm not sure the extra effort is worth it.

Forcing people to use the name mangling prefix is crummy though.

@xiazhvera xiazhvera merged commit 0c64f25 into main Dec 4, 2023
@xiazhvera xiazhvera deleted the mqtt5_ga_review branch December 4, 2023 22:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants