Currently, Mainflux mProxy hooks for intersecting different kinds of MQTT packets are written in such a way that we often don't return values or errors. While this is fine due to the nature of those methods, it makes sense that we return errors, values, or both to improve code testability.
Currently, Mainflux mProxy hooks for intersecting different kinds of MQTT packets are written in such a way that we often don't return values or errors. While this is fine due to the nature of those methods, it makes sense that we return errors, values, or both to improve code testability.