-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New api version #360
Comments
Nope. We haven’t broken compatibility with any existing add-ons, just added new APIs. You can feature detect the new APIs at runtime. |
But Is there an api which indicates which features are available? |
I kept backwards compatibility in place for the You can use a try/catch require for the new modules, that’s what I’ve done in other places. |
Sounds a bit messy. |
For new add-ons, they won’t fail, given that authors will be starting with 0.9. For existing add-ons, the authors should expect them to fail on pre-0.9, given that those APIs were not available when they created the add-on. |
But why not simply increase the version number? |
We really try not to bump the API version because every single add-on would need to be updated in order to run on the new gateway version. The gateway simply will not load an add-on if support for that API version is not declared. Would it help to provide a method in the gateway-addon packages that at least tells you the current API and package versions, and maybe even the gateway version? |
Damn, I forgot that the API version is also present in the It looks like the current concept of the API version is broken. I see three options:
What do you think? |
We're getting ready to rework the add-ons system quite a bit, since we're now adding different types of add-ons (notifiers, extensions (soon), services (soon)), and with that, we'll be bringing in a new manifest format based on the manifest.json format from WebExtensions. That would be a great opportunity to rework all of this. We'll be asking for feedback through that process, so please weigh in once we start! |
That sounds even better! |
This should help a tiny bit: WebThingsIO/gateway-addon-node#43 |
Now that there are changes in the protocol will there be a new API version?
The text was updated successfully, but these errors were encountered: