You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The loop function practically runs the SDK and makes the asynchronous behavior possible. User has to call it in the loop() of his/her Arduino sketch. It has nothing to do with a project, it's a function very specific to arduino architecture. Everywhere: on JS SDK and Py SDK, Project class provides access of and methods for interacting with the project space on Grandeur. loop isn't one of those.
My suggestion is, we keep Project, Device, Datastore classes pure and free of the architectural differences and move architecture-specific methods to Grandeur class. User would do grandeur.loop() instead.
The text was updated successfully, but these errors were encountered:
The
loop
function practically runs the SDK and makes the asynchronous behavior possible. User has to call it in theloop()
of his/her Arduino sketch. It has nothing to do with a project, it's a function very specific to arduino architecture. Everywhere: on JS SDK and Py SDK, Project class provides access of and methods for interacting with the project space on Grandeur.loop
isn't one of those.My suggestion is, we keep
Project
,Device
,Datastore
classes pure and free of the architectural differences and move architecture-specific methods toGrandeur
class. User would dograndeur.loop()
instead.The text was updated successfully, but these errors were encountered: