Skip to content

Conversation

@Governa
Copy link

@Governa Governa commented Oct 5, 2019

Always returning null breaks the contract set in the function signature
and documentation.

This affects all subscribes that receive IMqttMessageListener as parameter.

Please make sure that the following boxes are checked before submitting your Pull Request, thank you!

  • You have signed the Eclipse ECA
  • All of your commits have been signed-off with the correct email address (The same one that you used to sign the CLA)
  • If This PR fixes an issue, that you reference the issue below. OR if this is a new issue that you are fixing straight away that you add some Description about the bug and how this will fix it.
  • If this is new functionality, You have added the appropriate Unit tests.

Always returning null breaks the contract set in the function signature
and documentation.

This affects all subscribes that receive `IMqttMessageListener` as parameter.

Signed-off-by: Fernando Governatore <affqlixo+eclipse@gmail.com>
@Governa Governa force-pushed the null_on_subscribe_return branch from 6eedef3 to f19ada0 Compare October 5, 2019 00:41
  On subscribe, a failure would be reported but onSuccess would never be
called. The reason was not passing the IMqttActionListener forward to
MqttClient.

Signed-off-by: Fernando Governatore <affqlixo+eclipse@gmail.com>
@Governa Governa force-pushed the null_on_subscribe_return branch from da0468d to d87453c Compare October 10, 2019 19:20
@Governa
Copy link
Author

Governa commented Jun 12, 2020

Is this patch acceptable? Is there anything missing?

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.

1 participant