-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
che-editor
URL parameter should have higher priority than .che/che-editor.yaml
#21563
Comments
che-editor
URL parameter should have higher priority than .che/che-editor.yaml
I've tried the provided factory link |
@akurinnoy reopened for verification, the expected priority
|
Hello Team, I tried to reproduce this issue with below steps : Step 1] Set the
Step 2] Then created a repo with
Workspaces gets created with VScode IDE by default. So found that option Step 3] To check the priority of option "URL parameter for the workspace IDE" followed below steps :
Trying with URL paratmeter :
But I found that workspace is getting created with "Theia" IDE only. Further I also tried setting So found Attaching here some screenshots for reference. Let me know if any details required. Let me know if in case I am missing anything. |
need to make sure that we backport the fix to 7.60.x so that it would land in 3.5 |
Describe the bug
If I specify
che-editor
URL parameter I expect it to have higher priority compared to the editor specified in the git repository.che/che-editor.yaml
.Che version
next (development version)
Steps to reproduce
Start a workspace specifying the
che-editor
URL parameter using a git repository that contains a.che/che-editor.yaml
.For example, using the dogfooding Che instance, a repository that has a
.che/che-editor.yaml
where che-code is specified and the parameterche-editor=eclipse/che-theia/next
:https://che-dogfooding.apps.che-dev.x6e0.p1.openshiftapps.com/#https://github.com/l0rd/tilt-example-java/?che-editor=eclipse/che-theia/next
Expected behavior
The editor specified in the URL parameter should be used, not the one in the
.che/che-editor.yaml
file.Runtime
OpenShift
Screenshots
No response
Installation method
chectl/next
Environment
Amazon
Eclipse Che Logs
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: