...pub to .../modules has to happen to get modules updated.
Furthermore: the connect sets stuff in the SX127X... (writes to registers of XS127X) which has to rerun on every power cycle... This is in addition to the fact that that setting of stuff is done in an asynchronous matter... and that is the actual - compound - issue.
@gendor, for the SX127X init reason, it is a good practice to always have an onInit() construct in the code to ensure consistent behavior no matter what upload approach is used and power cycle.
@Gordon, what's the reason to not do simple callback to follow the prevailing pattern of .connect() (with undefined/err arg)? I'm aware of the callback hell... but at this point it is not hell yet and but I'm not sure if it is worth to complicated it that much with a Promise, even though it is more sophisticated.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
...pub to .../modules has to happen to get modules updated.
Furthermore: the connect sets stuff in the SX127X... (writes to registers of XS127X) which has to rerun on every power cycle... This is in addition to the fact that that setting of stuff is done in an asynchronous matter... and that is the actual - compound - issue.
@gendor, for the SX127X init reason, it is a good practice to always have an onInit() construct in the code to ensure consistent behavior no matter what upload approach is used and power cycle.
@Gordon, what's the reason to not do simple callback to follow the prevailing pattern of
.connect()
(with undefined/err arg)? I'm aware of the callback hell... but at this point it is not hell yet and but I'm not sure if it is worth to complicated it that much with a Promise, even though it is more sophisticated.