When we get back a response from the kai/rpc-server with a diff that represents a collection of changes. We need to expose this to the user in a consumable way. Breaking down the diff into different files where fixes need to be applied, maybe breaking up changes made to specific files...just making it so a user can act on what could be an overwhelming amount of information.
We must present the user with a set of changes with the option to accept/reject them.
When we get back a response from the kai/rpc-server with a diff that represents a collection of changes. We need to expose this to the user in a consumable way. Breaking down the diff into different files where fixes need to be applied, maybe breaking up changes made to specific files...just making it so a user can act on what could be an overwhelming amount of information.
We must present the user with a set of changes with the option to accept/reject them.