Add error handling to GattClient procedures
Open
enhancement
- Dominant language
- C++
- Stars
- 81
- Forks
- 71
- PR merge metrics
- No merged PRs in 30d
Description
With the current API their is no way to know if an error occur during the following GattClient procedures:
- `read`: If a read procedure fail, it should be possible to report this information to the application.
- `write`: If a write procedure fail, it should be possible to report this information to the application.
Contributor guide
Research direction
Start by locating the GattClient read and write procedure entry points and reviewing how their results currently reach the application. Define what failure information must be exposed for each procedure, then verify that both failed reads and failed writes can be distinguished from successful operations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- embedded-iot
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100