You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we are presenting the user with the response we got from the kai/rpc-server, one thing that would be really helpful is if the user could gain additional context on the proposed change by, clicking the filename for the codeblock or clicking the codeblock itself, opening that file in the editor where the proposed change is to be made. Additionally, we may elect to show the change in the editor with the option to accept/reject.
The text was updated successfully, but these errors were encountered:
Now that we have removed #69 from the minimum demoable thing, the scope of this effort has increased along with #67 , specifically this comment #67 (comment).
The important notes about how this effort has changed:
The webview will message the diff viewer with the proposed solution after kai/rpc-server has responded to our solution request and we have performed any necessary post processing.
The webview will be "disabled", preventing user input while the user works through the proposed solution.
The diff-viewer must notify the webview when the user has "finished" reconciling the proposed solution.
Most of the scope implemented in #79
The missing part is implementing the accept/reject buttons in the editor itself (i.e. code lense style). Right now it's implemented in the Konveyor Resolution view (native VS Code tree view).
When we are presenting the user with the response we got from the kai/rpc-server, one thing that would be really helpful is if the user could gain additional context on the proposed change by, clicking the filename for the codeblock or clicking the codeblock itself, opening that file in the editor where the proposed change is to be made. Additionally, we may elect to show the change in the editor with the option to accept/reject.
The text was updated successfully, but these errors were encountered: