-
Notifications
You must be signed in to change notification settings - Fork 52
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
fix: complete support of che-editor.yaml file #396
Conversation
Handle id, reference and inline and override properties Fixes eclipse-che/che#20715
Docker image build succeeded: quay.io/eclipse/che-dashboard:pr-396 |
✅ E2E dashboard tests succeed 🎉 See Details
Test product:
Eclipse Che QE channel: https://mattermost.eclipse.org/eclipse/channels/eclipse-che-qe |
This comment has been minimized.
This comment has been minimized.
Codecov Report
@@ Coverage Diff @@
## main #396 +/- ##
==========================================
- Coverage 48.81% 48.63% -0.19%
==========================================
Files 207 207
Lines 7180 7207 +27
Branches 1203 1214 +11
==========================================
Hits 3505 3505
- Misses 3301 3328 +27
Partials 374 374
Continue to review full report at Codecov.
|
it would be nice to have it included in the upcoming tag 7.39 |
repositoryEditorYamlUrl = cheEditorYaml.reference; | ||
} | ||
if (repositoryEditorYamlUrl) { | ||
const response = await this.axios.get<string>(repositoryEditorYamlUrl, { |
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 will cause 'has been blocked by CORS policy' error as we see with your example:
...
reference: https://eclipse-che.github.io/che-plugin-registry/main/v3/plugins/eclipse/che-theia/next/devfile.yaml
...
It should be done on the dashboard-backend
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.
@olexii4 it's strange, github.io is allowing CORS
requests are returning access-control-allow-origin: *
and it was working on my side
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 like this proposal. I have tested it. It works except CORS error which happens in the case with external reference (e.q. https://eclipse-che.github.io/che-plugin-registry/main/v3/plugins/eclipse/che-theia/next/devfile.yaml).
I agree to merge it if we open an issue to add tests for this important functionality (because we already have one regression eclipse-che/che#20737 with P1 and we should prevent it in the future).
@olexii4 it's not already handled by eclipse-che/che#20733 ? |
It is about IDE loading(IDE-loader) it is not cowering the Factory flow. But OK. I will add a comment to this issue. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: akurinnoy, benoitf, olexii4 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What does this PR do?
Handle id, reference, inline and override properties
What issues does this PR fix or reference?
Fixes eclipse-che/che#20715
Is it tested? How?
Tested with default samples and in addition:
Release Notes
Docs PR