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
Currently, this module just provides an invoke method so that any method from any version and protocol can be invoked without having each one being statically defined. The idea behind this is that no matter what firmware version or model you have the methods you have available to you are the ones you can invoke.
I wonder if it will make this module much easier to use if we define all the API methods and just throw a "not supported" exception for methods that might not actually be available? We could still provide the invoke method and under the hood could use the invoke method so they just become syntactical sugar in reality.
The text was updated successfully, but these errors were encountered:
Currently, this module just provides an invoke method so that any method from any version and protocol can be invoked without having each one being statically defined. The idea behind this is that no matter what firmware version or model you have the methods you have available to you are the ones you can invoke.
I wonder if it will make this module much easier to use if we define all the API methods and just throw a "not supported" exception for methods that might not actually be available? We could still provide the invoke method and under the hood could use the invoke method so they just become syntactical sugar in reality.
The text was updated successfully, but these errors were encountered: