-
Notifications
You must be signed in to change notification settings - Fork 667
CONSOLE-4407, CONSOLE-4409: Update monaco and YAML language server, use PF6 CodeEditor #14663
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
CONSOLE-4407, CONSOLE-4409: Update monaco and YAML language server, use PF6 CodeEditor #14663
Conversation
|
@logonoff: This pull request references CONSOLE-4407 which is a valid jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
3b9e426 to
03796ad
Compare
|
debt, adding labels /label px-approved |
spadgett
left a comment
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.
@logonoff Nice work!
Do we know if this impacts any public plugin APIs? It looks like we do expose Monaco options in the CodeEditor SDK component:
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.
Love seeing all of this code removed
|
And it looks like we expose the editor ref itself, so if there are breaking changes to the Monaco API, it can affect plugins. I think we have to bite the bullet if there are since not ever upgrading Monaco is not an option. We'll need to minimally release note this change, however. |
6c6d8c8 to
92b628b
Compare
92b628b to
e832153
Compare
|
QE review: /assign @yapei |
a50c157 to
8e2d1e0
Compare
8e2d1e0 to
b005a91
Compare
2b7a857 to
437c76f
Compare
|
@logonoff Are these two expected behaviors:
Screencast.From.2025-02-19.19-26-55.mp4
Screencast.From.2025-02-19.19-30-37.mp4 |
Yes, the Add cursor above option is supposed to create another cursor. This feature also exists in the current monaco editor
Yes, this behavior is consistent with the current monaco editor. I'll add a minimum height for the |
|
@logonoff: This pull request references CONSOLE-4407 which is a valid jira issue. This pull request references CONSOLE-4409 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
@logonoff check on cluster launched against the pr, tooltips will not show up for 'kind' and 'apiversion' on existing yaml file editor, when create new yaml, hover on 'kind' and 'apiversion', tooltips will show up. If it's an issue? Seems it occurs when yaml is long. Didn't reproduce with Secret and Configmap yaml. |
Hey @yanpzhan, I discussed with @jhadvig and it should be fine to not have the tooltips since the information is there on the autocomplete tooltip: There is a new feature, sticky scroll, that is introduced with this PR: Do you think that an option needs to exist to toggle it? I'm asking since we have a tooltip toggle as well, and I read in the ticket adding the toggle that it was because it takes up too much space in the UI and interferes with editing, which this feature might possibly interfere with as well. @jhadvig and I are leaning towards not adding a toggle, but I want to know your thoughts too |
|
@logonoff Thanks for your answer. The tooltip toggle helps when user edits the yaml, I'm happy if there is toggle for enabling/disabling 'sticky scroll', because I somehow don't care to know starting lines of currently visible nested contexts, and I feel the height of effective current lines are reduced. |
Thanks for your thoughts! Do you think it's okay to implement this in a follow up PR to avoid further increasing the scope of this large PR, and so I can also gather some thoughts from UX as well? Also, other than the issues mentioned, are there any other problems you've noticed with the updated CodeEditor? |
It's ok for me. |
|
@logonoff: This pull request references CONSOLE-4407 which is a valid jira issue. This pull request references CONSOLE-4409 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
3ddb0a9 to
313eed5
Compare
6126187 to
5734187
Compare
- Remove `Alt+F1` a11y help shortcut hint since the shortcut no longer exists in monaco - Fix long time bug where the commands in the command palette are bolded and underlined
5734187 to
c2d33df
Compare
TheRealJon
left a comment
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.
/lgtm
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: logonoff, TheRealJon The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@logonoff: This pull request references CONSOLE-4407 which is a valid jira issue. This pull request references CONSOLE-4409 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
@logonoff: This pull request references CONSOLE-4407 which is a valid jira issue. This pull request references CONSOLE-4409 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
@logonoff: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
[ART PR BUILD NOTIFIER] Distgit: openshift-enterprise-console |


















CONSOLE Features and Fixes:
https://issues.redhat.com/browse/CONSOLE-4407
https://issues.redhat.com/browse/CONSOLE-4409
Solution description
umd-compat-loaderScreen shots / gifs / design review:
Before:


After:

