Whenever CVP code is upgraded (either by the user on-prem, or automatically, on CVAAS), built-in studios are also upgraded. In some cases, the workspace containing that update may not be auto-submitted. There are typically one of two reasons behind this. Either the studio upgrade impact's device's running config (and we want the user to review the changes), or the new studio isn't building because of some error in the workspace.

Since Device Config diffing is a very important aspect of managing our hardware, we should make sure that this diffing is as convenient as possible. With that we have introduced a few improvements to our diffing component. These improvements range from UX convenience features to performance enhancers.