markiantorno / jdrfandroidbleparser Goto Github PK

Whatever names you want of course, but it looks like swallowing the exception is one of two viable options, some users might want any error to bubble up all the way immediately. What if you had one implementation:

override fun parse(c: BluetoothGattCharacteristic) {
            valueString = getNextStringValue(c)
}

and another:

fun tryParse(c: BluetoothGattCharacteristic) {
    try { parse(c) } catch() ...
}

This interface would be in the BaseCharacteristic and each subclass would only need to override the parse, the tryParse could be overridden if custom error reporting or something is desired.