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
{{ message }}
This repository has been archived by the owner on Jun 2, 2023. It is now read-only.
We currently have folders with the name of the hardware corresponding to each translator (without namespacing) under each schema folder.
E.g. here we have folders like “Philips Hue Light Bulb” and “Osram Lightify Light Bulb”. These names are not namespaced, unlike schema names which are namespaced.
We need to update all the translator names to reverse URI based names, just like the schemas. The name of the hardware and the npm package name should be included in the package.json as description and name, respectively.
This will be a pretty disruptive change for anyone who depends on translators and the current structure of the repo, so we will need to make sure all dependencies are updated at the same time.
The text was updated successfully, but these errors were encountered:
tjaffri
changed the title
Update the directory structure of translators repo to use revese URI based names for translators
Update the directory structure of translators repo to use reverse URI based names for translators
Aug 13, 2016
Move all reverse-uri naming schemes to lowercase (schema and translator folder names)
Tweak the names a little to use the "org.opent2t.sample.thermostat.superpopular" convention. This way they are still readable on GitHub but also following a naming hierarchy.
We currently have folders with the name of the hardware corresponding to each translator (without namespacing) under each schema folder.
E.g. here we have folders like “Philips Hue Light Bulb” and “Osram Lightify Light Bulb”. These names are not namespaced, unlike schema names which are namespaced.
We need to update all the translator names to reverse URI based names, just like the schemas. The name of the hardware and the npm package name should be included in the package.json as description and name, respectively.
This will be a pretty disruptive change for anyone who depends on translators and the current structure of the repo, so we will need to make sure all dependencies are updated at the same time.
The text was updated successfully, but these errors were encountered: