We shouldn't be using (most) of this code directly in mash. Getting this right and easily enforced may require moving some files. For example, enums are likely fine.
I could see making two targets, where things like DeviceDataManager/DeviceHotplugEventObserver/etc. should be not used in ash/chrome. The other half, InputDeviceManager/InputDevice/TouchscreenDevice/etc. is more client-y code though?
Comment 1 by kylec...@chromium.org
, Jul 24 2017