I think SwiftyTeeth might be better served as being a set of convenience extensions/classes to CoreBluetooth instead of ever really "hiding" any functionality...
I'm on the fence about this, but I think for future-proofing, and reducing possible blockers by any consumers, this should really just extend the underlying CB.
It does mean accepting a lot of the crappy API CoreBluetooth puts forward, but maybe there is a happy middle ground.
I think SwiftyTeeth might be better served as being a set of convenience extensions/classes to CoreBluetooth instead of ever really "hiding" any functionality...
I'm on the fence about this, but I think for future-proofing, and reducing possible blockers by any consumers, this should really just extend the underlying CB.
It does mean accepting a lot of the crappy API CoreBluetooth puts forward, but maybe there is a happy middle ground.