Which area/kind this issue is related to?
/area registry
Issue Description
We have recently updated the projectType and language values in the community registry to better reflect the content of the devfile (devfile/registry@f68bcdf). However, some of the starter projects that includes a devfile has not been updated with the same change, e.g. https://github.com/nodeshift-starters/devfile-sample/blob/main/devfile.yaml still uses nodejs as both projectType and language instead of Node.js and JavaScript. We need to go through all the starter projects to make sure they match the value of the devfile from the supporting stacks.
This item is not restricted to the nodejs sample. We should check the other ones as well.
When making the change, we need to make sure it doesn't cause problems with test automation (both devfile project and other tools like odo, ODC, App Studio, etc.. in case any of the existing tests are relying on those values.
Which area/kind this issue is related to?
/area registry
Issue Description
We have recently updated the projectType and language values in the community registry to better reflect the content of the devfile (devfile/registry@f68bcdf). However, some of the starter projects that includes a devfile has not been updated with the same change, e.g. https://github.com/nodeshift-starters/devfile-sample/blob/main/devfile.yaml still uses
nodejsas both projectType and language instead ofNode.jsandJavaScript. We need to go through all the starter projects to make sure they match the value of the devfile from the supporting stacks.This item is not restricted to the nodejs sample. We should check the other ones as well.
When making the change, we need to make sure it doesn't cause problems with test automation (both devfile project and other tools like odo, ODC, App Studio, etc.. in case any of the existing tests are relying on those values.