| Commit-Queue | +1 |
I found that there's also chrome/browser/ui/ash/magic_boost/magic_boost_constants.h which defines namespace chromeos::magic_boost.
How about merging them, or at least stick to a single namespace, in a followup CL?
views::Widget* disclaimer_widget_for_test() {In a followup-CL I'll want to make this private or delete it or remove the MagicBoostControllerAshTest friend declaration.
class MagicBoostControllerAsh {In a followup-CL I want to drop the Ash suffix from the name.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
I found that there's also chrome/browser/ui/ash/magic_boost/magic_boost_constants.h which defines namespace chromeos::magic_boost.
How about merging them, or at least stick to a single namespace, in a followup CL?
sgtm
views::Widget* disclaimer_widget_for_test() {In a followup-CL I'll want to make this private or delete it or remove the MagicBoostControllerAshTest friend declaration.
Acknowledged
class MagicBoostControllerAsh {In a followup-CL I want to drop the Ash suffix from the name.
Acknowledged
class MockMagicBoostController : public ash::MagicBoostControllerAsh {inheriting concrete class for Mock often has problematic behavior.
Can we keep separating interface and concrete class?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |