dididy opened a new pull request, #5064:
URL: https://github.com/apache/zeppelin/pull/5064

   ### What is this PR for?
   Unlike the Classic UI, the New UI either lacked implementations for several 
shortcuts or had shortcuts assigned differently from the Classic UI. I consider 
this a significant issue, and after addressing other related derivative issues, 
I am finally submitting it.
   
   The distinction between command mode and edit mode for shortcuts was 
meaningless, so it was removed. The original implementation seemed intended to 
mimic a vi-like behavior, but this would have made the shortcut system 
different from the Classic UI.
   
   In the Classic UI, Auto Completion had a shortcut to trigger it manually. In 
the New UI, auto completion is triggered automatically when typing, so the 
shortcut was unnecessary and has been removed in this PR.
   
   #### d96ae5bde - Remove the top margin in the editor search
   [AS-IS]
   <img width="671" height="136" alt="스크린샷 2025-09-01 오후 11 26 14" 
src="https://github.com/user-attachments/assets/fcd0a107-4b22-42f2-978f-f0781c5fd675";
 />
   [TO-BE]
   <img width="669" height="136" alt="스크린샷 2025-09-01 오후 11 26 23" 
src="https://github.com/user-attachments/assets/475c05e6-ffae-4410-920f-7b0a9e44388d";
 />
   
   Fixed an issue where the top area increased by 33px when search was 
activated. <- 
[referece](https://github.com/microsoft/monaco-editor/blob/5a7ba61be909ae9e4889768a3453ebb0dec392e2/monaco-editor/typedoc/monaco.d.ts#L3473)
   
   #### 0d24eb420 - Handle focus on PARAGRAPH_MOVED receive
   When performing "Move Paragraph Up" or "Move Paragraph Down," the paragraph 
moves up or down after receiving `PARAGRAPH_MOVED`. During this process, focus 
was being skipped, so I added it.
   
   #### 1d3d294bc - Overriding shortcuts conflict with the editor
   In the New UI, we use the Monaco editor, where reserved shortcuts had to be 
explicitly overridden. I added shortcut functionality for four actions: "Toggle 
Editor", "Cut the Line", "Paste the Line", and "Search Inside the Code".
   
   #### 57f45e1e8 - Make action bar searchCode accessible to siblings
   There are `paragraph.component.ts` and `action-bar.component.ts` that share 
`notebook.component.ts` as their parent. In the Classic UI, "Find in Code" is a 
shortcut that activates the search button in the action-bar. Although this 
functionality is currently marked as TODO in the New UI, I set up the 
connection by adding a Template Reference Variable and Event Binding in 
`notebook.component.html`. With this setup, `paragraph.component.ts` can invoke 
the **searchCode()** method of `action-bar.component.ts`.
   
   #### 1df52d7e9 - Ensure shortcut keys work correctly
   <img width="605" height="1088" alt="image" 
src="https://github.com/user-attachments/assets/2c4bc264-07e5-4abe-93bb-a2656a86527b";
 />
   
   All shortcut orders have been updated based on the Classic UI. There was 
logic to handle key bindings differently for macOS, but upon review, it was 
unnecessary and has been removed. On macOS, typing a combination of Alt and an 
English letter can produce a different character, so to ensure correct 
behavior, this resulting character combination is included in the shortcut 
handling. I added several actions that were not yet implemented.
   
   ### What type of PR is it?
   Bug Fix
   
   ### Todos
   
   ### What is the Jira issue?
   * [[ZEPPELIN-6197](https://issues.apache.org/jira/browse/ZEPPELIN-6197)]
   * [[ZEPPELIN-6229](https://issues.apache.org/jira/browse/ZEPPELIN-6229)]
   
   ### How should this be tested?
   
   ### Screenshots (if appropriate)
   
   ### Questions:
   * Does the license files need to update? N
   * Is there breaking changes for older versions? N
   * Does this needs documentation? N
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: reviews-unsubscr...@zeppelin.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to