MarionetteLabs/marionette.inspector — pull request #18 by jasonLaster (2014-10-24 15:31:59+00:00)
Title: Cleanup component reports

So, our component reports were kinda a mess.

My understanding, is that the thinking was that the backboneAgent would send a report for every action, change, and new event. Interestingly, these reports did not have much information so the panel would be responsible for doing a secondary request for more details.

This hasn't really affected us, because while the InspectedPage was receiving all of the reports, we were not doing anything with them.

This cleanup, is a first step towards making the reports useful to the Inspector so that we can take action based on what's happening to the app.

Three things went into this change:

1. reports now have a type and name field
+ in the case of a `trigger` action the type is `trigger` and the name is the event like `before:show`

2. devTools listens to reports
+ there's a new `ComponentReportToRegionTreeMap` that listens to reports and checks to see if the regionTree updated

3. the EventInterceptor is killed
+ now that we're using the reports, we don't need to use the interceptor to send regionTree messages