Inject Bluetooth Devices as Spezi Modules #32
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Inject Bluetooth Devices as Spezi Modules
♻️ Current situation & Problem
BluetoothDevice
s were previously inaccessible from SpeziModule
s without additional infrastructure. StanfordSpezi/Spezi#105 introduced functionality to dynamically load and unload Modules from the Spezi module systems. We use that new infrastructure to make everyBluetoohtDevice
to be a Spezi Module.This allows every
BluetoothDevice
to use the same functionality available to Spezi Modules. Further, Spezi Modules can seamlessly interact withBluetoothDevice
as well.⚙️ Release Notes
BluetoothDevice
s are now SpeziModule
s.📚 Documentation
Additional documentation section was added.
✅ Testing
Verified in Engage.
📝 Code of Conduct & Contributing Guidelines
By submitting creating this pull request, you agree to follow our Code of Conduct and Contributing Guidelines: