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.
Many manifest.xml files are missing resources referenced by their platform schemas. This file is read by the LocalPackageSource and in order to create the translator packages, so as a result our translators are incomplete. Manifest.xml must list all dependencies (like core, base, resource, link, wk.d, wk.p, etc). OcfSchemaReader already exists in the opent2t library to dereference JSON schemas. This could be used to generate a list of dependencies rather than having to explicitely call them out in the manifest. The current way of doing this tries to keep the same information in at least two places.
Using OcfSchemaReader to dereference a platform schema (like org.opent2t.sample.lamp.superpopular) fails at this point because it cannot find the referenced schemas.
colourRGB is also mispelled.
I recommend that we move all resource definitions under another folder (translators/resources). They only exist at the root for pack-translator.js to pick up. Otherwise, it needlessly increases the number of directories in the translators repo.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Many manifest.xml files are missing resources referenced by their platform schemas. This file is read by the LocalPackageSource and in order to create the translator packages, so as a result our translators are incomplete. Manifest.xml must list all dependencies (like core, base, resource, link, wk.d, wk.p, etc). OcfSchemaReader already exists in the opent2t library to dereference JSON schemas. This could be used to generate a list of dependencies rather than having to explicitely call them out in the manifest. The current way of doing this tries to keep the same information in at least two places.
Using OcfSchemaReader to dereference a platform schema (like org.opent2t.sample.lamp.superpopular) fails at this point because it cannot find the referenced schemas.
colourRGB is also mispelled.
I recommend that we move all resource definitions under another folder (translators/resources). They only exist at the root for pack-translator.js to pick up. Otherwise, it needlessly increases the number of directories in the translators repo.
The text was updated successfully, but these errors were encountered: