-
Notifications
You must be signed in to change notification settings - Fork 111
fix(workpace-plugin): Importing several private projects in a single devfile #959
fix(workpace-plugin): Importing several private projects in a single devfile #959
Conversation
❌ E2E Happy path tests failed ❗ See Details
Tested with Eclipse Che Single User on K8S (minikube v1.1.1)
|
[crw-ci-test] |
❌ E2E Happy path tests failed ❗ See Details
Tested with Eclipse Che Single User on K8S (minikube v1.1.1)
|
[crw-ci-test] |
FYI I switched happy path channel to |
✅ E2E Happy path tests succeed 🎉 See Details
Tested with Eclipse Che Single User on K8S (minikube v1.1.1)
|
@@ -0,0 +1,72 @@ | |||
apiVersion: 1.0.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure it's a good practice to introduce devfiles in each directory ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This a devfile to work on the workspace plugin, as this project lives in a subdirectory of the git repo, it looks good to have it there, next to the package.json, etc ...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
but it's part of a yarn workspace so you should use top-level folder/definitions/devfile anyway to inherits from all workspace definition
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok but isn't it overkill when a dev just want to work on 1 plugin ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It might be useful to have the devfile here, even just for reference purposes. It could be useful to point for new contributors in the future.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This devfile is for coding the workspace plugin without having to rebuild che-theia and all the other plugins. It doesn't make sense to have it elsewhere.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The maintenance issue is not related to the location of the devfiles. but how a devfile could be extended: so the devfile for the workspace plugin (that would be in the workspace plugin folder) could extend a more generic devfile for built-in plugins but adding its own specifics (for instance, custom commands, etc ...). Maybe it is in the scope of devfile 2.
Parent pom.xml files are usually there to share BoM. But without these sharing capabilities, we would have pom.xml files for each module that would be also hard to maintain. Anyway a module would have its own pom.xml.
Anyway, the devfile for the workspace plugin has to stay here because it would setup the right workspace for the workspace-plugin developer flow.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and then if the suggestion is to move that devfile to the devfiles
directory I don't see how easier it would be to maintain. Or is the suggestion not to have devfile at all and let all the developers loosing time to setup an dev environment to work on each individual plugins?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, the suggestion is to have a a single devfile for developing che-theia.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there is that devfile https://github.com/eclipse/che-theia/blob/master/devfiles/che-theia-all.devfile.yaml but it is doing way too many things when it is to work a a particular plugin.
@@ -8,6 +8,8 @@ | |||
* SPDX-License-Identifier: EPL-2.0 | |||
***********************************************************************/ | |||
|
|||
import 'jest'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks odd to import jest
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was the only way I could find to get rid of the errors reported by the typescript plugin.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
but jest is added on tsconfig types
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could you add
"types": ["reflect-metadata", "jest"],
in https://github.com/eclipse/che-theia/blob/master/plugins/workspace-plugin/tsconfig.json ?
like it's done there: https://github.com/eclipse/che-theia/blob/master/plugins/ports-plugin/tsconfig.json#L12-L14
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tried that already (see the M in tsconfig.ts in the screenshoft above). And just retried but it doesn't get rid of the error message. Maybe a bug in the plugin.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@benoitf I rebased and removed the imports
✅ E2E Happy path tests succeed 🎉 See Details
Tested with Eclipse Che Single User on K8S (minikube v1.1.1)
|
…devfile Signed-off-by: Sun Tan <sutan@redhat.com>
Signed-off-by: Sun Tan <sutan@redhat.com>
Signed-off-by: Sun Tan <sutan@redhat.com>
Signed-off-by: Sun Tan <sutan@redhat.com>
3bda7d6
to
004edb9
Compare
Signed-off-by: Sun Tan <sutan@redhat.com>
✅ E2E Happy path tests succeed 🎉 See Details
Tested with Eclipse Che Single User on K8S (minikube v1.1.1)
|
@sunix there is still the devfile |
I thought we were ok
|
What does this PR do?
devfile.yaml
for the workspace plugin (simplify review).Fix jest import errors in CheWhat issues does this PR fix or reference?
Fix eclipse-che/che#18494
How to test this PR?
/tmp/theiadev_projects
from a terminal of che-theia-next-dev cotainer.PR Checklist
As the author of this Pull Request I made sure that:
What issues does this PR fix or reference
andHow to test this PR
completedReviewers
Reviewers, please comment how you tested the PR when approving it.
Happy Path Channel
HAPPY_PATH_CHANNEL=next