Closed jmuharsky closed 9 years ago
LGTM.
Optionally, consider squashing these changes and deferring merging this until you have implemented a use case for it. Personally I often find myself needing to make changes to APIs once they get used in practice. But it's also ok to make needed fixes later.
That's fair. In actuality, the branch router_widgetselect has the "in practice" integration. This PR represents a cleanup after getting it all working.
Adds the management classes (Service and Model) for Explorer State, based on the current values in the Angular UI Router state service. At the moment, these services are loaded but unused; additional PR's will consolidate the dashboard's selection state into this service.
For more info, see the Design Doc