fazho
fazho
@chkr1011 Could you please take a look?
It's the same reason why we have a Connecting event, which happens right after the connection status is transitioned into Connecting but the work of connecting to the server has...
Basically it guarantees us an early access to the reason code in the DISCONNECT packet when server disconnects the client.
@chkr1011 could you let me know if my comments address your concern?
@chkr1011 could you take another look?
@chkr1011 Addressed your comments. Could you please take another look?
@chkr1011 that's even better. If I understand correctly, you are saying we should catch the exception from Publish, and re-throw a specific exception type (for example, MqttClientUnexpectedDisconnectReceivedException) that could contain...
@chkr1011 I sent out another PR: https://github.com/dotnet/MQTTnet/pull/1974. Could you let me know if this meets your expectation?
@chkr1011 No we don't need this PR given the new one: https://github.com/dotnet/MQTTnet/pull/1974