Open
Description
#1962 starts work toward this and highlights differences between where we want to emit a targets update and where we want to emit a project changed event. These sometimes coincide but not always and it would be explicit about what change occurs where and track these two different kinds of changes separately.
Doing this will also address the comment linked below where we are emitting targets update from the runtime, and for now anytime this happens, we are explicitly not emitting a project changed event. Removing the extra emitting project changed functionality will allow us to clean up this line of code a bit more:
CC/ @chrisgarrity