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
Our initial intention with the API was to prefix all properties and methods that are not datatypes with $. The reason for this was to remove the possibility of a naming conflict between a datatype name and a property or method on the API. We have forgotten about this with some of our naming:
project.deviceId
project.importConfig()
project.ready()
project.close()
I think the original intention and reasoning was valid, so I think we should rename these properties and methods. This will be a breaking change for the API, but should be easy to manage because we ship the API with the app. This is non-urgent, but I think worth addressing at some point.
The text was updated successfully, but these errors were encountered:
Our initial intention with the API was to prefix all properties and methods that are not datatypes with
$
. The reason for this was to remove the possibility of a naming conflict between a datatype name and a property or method on the API. We have forgotten about this with some of our naming:project.deviceId
project.importConfig()
project.ready()
project.close()
I think the original intention and reasoning was valid, so I think we should rename these properties and methods. This will be a breaking change for the API, but should be easy to manage because we ship the API with the app. This is non-urgent, but I think worth addressing at some point.
The text was updated successfully, but these errors were encountered: