Framework Introduce CallbackWrapper
there is a bunch of profiles that register callback to the bluetooth service, this logic is repeated again and again. By having a common wrapper we can: * Finnaly have some tests on the registration logic (none before) * Make sure all the profile are registering callback the same ways * remove duplicates code This initial CL only implement it for HAP, other profiles will be done in follow up Bug: 311772251 Flag: Exempt no-op refactor Test: atest FrameworkBluetoothTests Change-Id: I61f3fdfb82efd26435ce8d9c74509708aca58b0d
Loading
Please register or sign in to comment