Improve windows device name discovery

Type

Enhancement

Description

Updated the Pigeon version in the autogenerated comments in universal_ble.g.cpp, UniversalBle.g.kt, and universal_ble.g.h.
Renamed the included header files in universal_ble.g.cpp, universal_ble_plugin_c_api.cpp, and utils.h to match the new file structure.
Added a new function CreateConnectionError in universal_ble.g.cpp and createConnectionError in UniversalBle.g.kt to generate a FlutterError with a specific message.
Refactored the channel creation and error handling in multiple functions in universal_ble.g.cpp and UniversalBle.g.kt to use the new error creation function.
Removed an unnecessary comment in utils.cpp.
Added a new file ui_thread_handler.hpp which defines a class UniversalBleUiThreadHandler for handling UI thread related tasks.
Reformatted the UniversalBlePluginCApiRegisterWithRegistrar function in universal_ble_plugin_c_api.cpp for better readability.
Updated the output paths for the generated C++ header and source files in universal_ble.dart to match the new file structure.
Removed the ConnectionStateStruct, PairStateStruct, and ValueChangeStruct structs in utils.h.
Updated the header guard in universal_ble.g.h to match the new file name.

Changes walkthrough

Relevant files

Error handling

universal_ble.g.cpp

Improved error handling and updated Pigeon version in 

 universal_ble.g.cpp

windows/src/generated/universal_ble.g.cpp - Updated the Pigeon version in the autogenerated comment. - Renamed the included header file to match the new file structure. - Added a new function `CreateConnectionError` to generate a
`FlutterError` with a specific message. - Refactored the `channel` creation and error handling in multiple
functions to use the new `CreateConnectionError` function.

+34/-22

UniversalBle.g.kt

Improved error handling and updated Pigeon version in UniversalBle.g.kt

android/src/main/kotlin/com/navideck/universal_ble/UniversalBle.g.kt - Updated the Pigeon version in the autogenerated comment. - Added a new function `createConnectionError` to generate a
`FlutterError` with a specific message. - Refactored the `channel` creation and error handling in multiple
functions to use the new `createConnectionError` function.

+39/-26

Miscellaneous

utils.cpp `Removed unnecessary comment in utils.cpp` windows/src/helper/utils.cpp - Removed an unnecessary comment.	+1/-9
utils.h `Removed unused structs and updated header file in utils.h` windows/src/helper/utils.h - Updated the included header file to match the new file structure. - Removed the `ConnectionStateStruct`, `PairStateStruct`, and ` ``ValueChangeStruct` structs.	+2/-31
universal_ble.g.h `Updated Pigeon version and header guard in universal_ble.g.h` windows/src/generated/universal_ble.g.h - Updated the Pigeon version in the autogenerated comment. - Updated the header guard to match the new file name.	+4/-4

Enhancement

ui_thread_handler.hpp

Added new UI thread handler class

windows/src/ui_thread_handler.hpp - Added a new file `ui_thread_handler.hpp` which defines a class
`UniversalBleUiThreadHandler` for handling UI thread related tasks.

+79/-0

Formatting

universal_ble_plugin_c_api.cpp

Updated header file and reformatted function in 

 universal_ble_plugin_c_api.cpp

windows/universal_ble_plugin_c_api.cpp - Updated the included header file to match the new file structure. - Reformatted the `UniversalBlePluginCApiRegisterWithRegistrar` function
for better readability.

+6/-5

Configuration changes

universal_ble.dart

Updated output paths in universal_ble.dart

pigeon/universal_ble.dart - Updated the output paths for the generated C++ header and source files
to match the new file structure.

+2/-2

✨ Usage guide:

**Overview:** The `describe` tool scans the PR code changes, and generates a description for the PR - title, type, summary, walkthrough and labels. The tool can be triggered [automatically](https://github.com/Codium-ai/pr-agent/blob/main/Usage.md#github-app-automatic-tools) every time a new PR is opened, or can be invoked manually by commenting on a PR. When commenting, to edit [configurations](https://github.com/Codium-ai/pr-agent/blob/main/pr_agent/settings/configuration.toml#L46) related to the describe tool (`pr_description` section), use the following template: ``` /describe --pr_description.some_config1=... --pr_description.some_config2=... ``` With a [configuration file](https://github.com/Codium-ai/pr-agent/blob/main/Usage.md#working-with-github-app), use the following template: ``` [pr_description] some_config1=... some_config2=... ```

Enabling\disabling automation

- When you first install the app, the [default mode](https://github.com/Codium-ai/pr-agent/blob/main/Usage.md#github-app-automatic-tools) for the describe tool is: ``` pr_commands = ["/describe --pr_description.add_original_user_description=true" "--pr_description.keep_original_user_title=true", ...] ``` meaning the `describe` tool will run automatically on every PR, will keep the original title, and will add the original user description above the generated description. - Markers are an alternative way to control the generated description, to give maximal control to the user. If you set: ``` pr_commands = ["/describe --pr_description.use_description_markers=true", ...] ``` the tool will replace every marker of the form `pr_agent:marker_name` in the PR description with the relevant content, where `marker_name` is one of the following: - `type`: the PR type. - `summary`: the PR summary. - `walkthrough`: the PR walkthrough. Note that when markers are enabled, if the original PR description does not contain any markers, the tool will not alter the description at all.

Custom labels

The default labels of the `describe` tool are quite generic: [`Bug fix`, `Tests`, `Enhancement`, `Documentation`, `Other`]. If you specify [custom labels](https://github.com/Codium-ai/pr-agent/blob/main/docs/DESCRIBE.md#handle-custom-labels-from-the-repos-labels-page-gem) in the repo's labels page or via configuration file, you can get tailored labels for your use cases. Examples for custom labels: - `Main topic:performance` - pr_agent:The main topic of this PR is performance - `New endpoint` - pr_agent:A new endpoint was added in this PR - `SQL query` - pr_agent:A new SQL query was added in this PR - `Dockerfile changes` - pr_agent:The PR contains changes in the Dockerfile - ... The list above is eclectic, and aims to give an idea of different possibilities. Define custom labels that are relevant for your repo and use cases. Note that Labels are not mutually exclusive, so you can add multiple label categories. Make sure to provide proper title, and a detailed and well-phrased description for each label, so the tool will know when to suggest it.

Inline File Walkthrough 💎

For enhanced user experience, the `describe` tool can add file summaries directly to the "Files changed" tab in the PR page. This will enable you to quickly understand the changes in each file, while reviewing the code changes (diffs). To enable inline file summary, set `pr_description.inline_file_summary` in the configuration file, possible values are: - `'table'`: File changes walkthrough table will be displayed on the top of the "Files changed" tab, in addition to the "Conversation" tab. - `true`: A collapsable file comment with changes title and a changes summary for each file in the PR. - `false` (default): File changes walkthrough will be added only to the "Conversation" tab.

Utilizing extra instructions

The `describe` tool can be configured with extra instructions, to guide the model to a feedback tailored to the needs of your project. Be specific, clear, and concise in the instructions. With extra instructions, you are the prompter. Notice that the general structure of the description is fixed, and cannot be changed. Extra instructions can change the content or style of each sub-section of the PR description. Examples for extra instructions: ``` [pr_description] extra_instructions=""" - The PR title should be in the format: ': ' - The title should be short and concise (up to 10 words) - ... """ ``` Use triple quotes to write multi-line instructions. Use bullet points to make the instructions more readable. </details></td></tr> <tr><td><details> <summary><strong> More PR-Agent commands</strong></summary><hr> > To invoke the PR-Agent, add a comment using one of the following commands: > - **/review**: Request a review of your Pull Request. > - **/describe**: Update the PR title and description based on the contents of the PR. > - **/improve [--extended]**: Suggest code improvements. Extended mode provides a higher quality feedback. > - **/ask \<QUESTION\>**: Ask a question about the PR. > - **/update_changelog**: Update the changelog based on the PR's contents. > - **/add_docs** 💎: Generate docstring for new components introduced in the PR. > - **/generate_labels** 💎: Generate labels for the PR based on the PR's contents. > - **/analyze** 💎: Automatically analyzes the PR, and presents changes walkthrough for each component. >See the [tools guide](https://github.com/Codium-ai/pr-agent/blob/main/docs/TOOLS_GUIDE.md) for more details. >To list the possible configuration parameters, add a **/config** comment. </details></td></tr> </table> See the [describe usage](https://github.com/Codium-ai/pr-agent/blob/main/docs/DESCRIBE.md) page for a comprehensive guide on using this tool. </details> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/codiumai-pr-agent[bot]"><img src="https://avatars.githubusercontent.com/in/354216?v=4" />codiumai-pr-agent[bot]</a> commented <strong> 3 months ago</strong> </div> <div class="markdown-body"> <p><strong><a href="https://github.com/Navideck/universal_ble/pull/4">PR Description</a></strong> updated to latest commit (<a href="https://github.com/Navideck/universal_ble/commit/bffd894e97730d93352dbacbc7a8b81d37134d52">https://github.com/Navideck/universal_ble/commit/bffd894e97730d93352dbacbc7a8b81d37134d52</a>)</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/codiumai-pr-agent[bot]"><img src="https://avatars.githubusercontent.com/in/354216?v=4" />codiumai-pr-agent[bot]</a> commented <strong> 3 months ago</strong> </div> <div class="markdown-body"> <h2>PR Analysis</h2> <h3>(review updated until commit <a href="https://github.com/Navideck/universal_ble/commit/a47f20fa6af38c0f265b5805ecb52ae4462d2a61">https://github.com/Navideck/universal_ble/commit/a47f20fa6af38c0f265b5805ecb52ae4462d2a61</a>)</h3> <ul> <li>🎯 <strong>Main theme:</strong> Enhancing Bluetooth device discovery and connection handling in the Windows implementation</li> <li>📝 <strong>PR summary:</strong> This PR focuses on improving the Bluetooth device discovery and connection handling for the Windows implementation. It introduces new keys for device properties, modifies the BluetoothLEWatcher setup, and adds methods for parsing manufacturer data and Bluetooth device ID. It also includes error handling in the ConnectAsync method and modifies various methods for additional checks and data parsing.</li> <li>📌 <strong>Type of PR:</strong> Enhancement</li> <li>🧪 <strong>Relevant tests added:</strong> No</li> <li>⏱️ <strong>Estimated effort to review [1-5]:</strong> 4, because the PR contains a significant amount of changes in multiple files, including the addition of new methods and modifications to existing ones. It also involves understanding the Bluetooth device discovery and connection handling process.</li> <li>🔒 <strong>Security concerns:</strong> No security concerns found <h2>PR Feedback</h2></li> </ul> <p><strong>💡 General suggestions:</strong> The PR is well-structured and the changes are logically grouped. However, it would be beneficial to include tests to verify the new functionality and changes. Additionally, it would be helpful to provide more context or comments in the code to explain the purpose and functionality of the new methods and changes, especially for those unfamiliar with Bluetooth device discovery and connection handling.</p> <details><summary> <strong>🤖 Code feedback:</strong></summary><hr><table><tr><td>relevant file</td><td>windows/src/generated/universal_ble.g.cpp</td></tr><tr><td>suggestion </td><td><br> **It's good to see that error messages are being made more specific by including the channel name. However, it would be beneficial to also include the specific error that occurred during the connection attempt. This would make debugging easier and more efficient. [medium]** <br></td></tr><tr><td>relevant line</td><td><a href='https://github.com/Navideck/universal_ble/pull/4/files#diff-92e69b3dc0c97a5367d2a46ee4a042924534973f5adbc808f2ba303168895f45R837'>on_error(CreateConnectionError(channel_name));</a></td></tr></table><hr><table><tr><td>relevant file</td><td>windows/src/universal_ble_plugin.h</td></tr><tr><td>suggestion </td><td><br> **The `BluetoothDeviceAgent` struct seems to be doing a lot of work. It might be beneficial to break down its responsibilities into smaller, more manageable classes or structs. This would make the code more readable and maintainable. [medium]** <br></td></tr><tr><td>relevant line</td><td><a href='https://github.com/Navideck/universal_ble/pull/4/files#diff-5e53d816e18b3a55d63090396aac40ab0c2159f0bf24d5ae5687d003c22c809fR38'>struct BluetoothDeviceAgent</a></td></tr></table><hr><table><tr><td>relevant file</td><td>windows/src/universal_ble_plugin.h</td></tr><tr><td>suggestion </td><td><br> **The `BluetoothDeviceAgent` struct has a method `_fetch_characteristic` that throws an error if a service or characteristic is not found. It would be more efficient to return a `nullptr` or an optional instead of throwing an error. This would allow the caller to handle the absence of a service or characteristic in a more controlled manner. [medium]** <br></td></tr><tr><td>relevant line</td><td><a href='https://github.com/Navideck/universal_ble/pull/4/files#diff-5e53d816e18b3a55d63090396aac40ab0c2159f0bf24d5ae5687d003c22c809fR54'>GattCharacteristicObject &_fetch_characteristic(const std::string &service_uuid,</a></td></tr></table><hr><table><tr><td>relevant file</td><td>windows/src/universal_ble_plugin.h</td></tr><tr><td>suggestion </td><td><br> **The `UniversalBlePlugin` class has a lot of responsibilities. It might be beneficial to break down its responsibilities into smaller, more manageable classes. This would make the code more readable and maintainable. [important]** <br></td></tr><tr><td>relevant line</td><td>class UniversalBlePlugin</td></tr></table><hr></details> <hr> <details> <summary><strong>✨ Usage guide:</strong></summary><hr> **Overview:** The `review` tool scans the PR code changes, and generates a PR review. The tool can be triggered [automatically](https://github.com/Codium-ai/pr-agent/blob/main/Usage.md#github-app-automatic-tools) every time a new PR is opened, or can be invoked manually by commenting on any PR. When commenting, to edit [configurations](https://github.com/Codium-ai/pr-agent/blob/main/pr_agent/settings/configuration.toml#L19) related to the review tool (`pr_reviewer` section), use the following template: ``` /review --pr_reviewer.some_config1=... --pr_reviewer.some_config2=... ``` With a [configuration file](https://github.com/Codium-ai/pr-agent/blob/main/Usage.md#working-with-github-app), use the following template: ``` [pr_reviewer] some_config1=... some_config2=... ``` <table><tr><td><details> <summary><strong> Utilizing extra instructions</strong></summary><hr> The `review` tool can be configured with extra instructions, which can be used to guide the model to a feedback tailored to the needs of your project. Be specific, clear, and concise in the instructions. With extra instructions, you are the prompter. Specify the relevant sub-tool, and the relevant aspects of the PR that you want to emphasize. Examples for extra instructions: ``` [pr_reviewer] # /review # extra_instructions=""" In the 'general suggestions' section, emphasize the following: - Does the code logic cover relevant edge cases? - Is the code logic clear and easy to understand? - Is the code logic efficient? ... """ ``` Use triple quotes to write multi-line instructions. Use bullet points to make the instructions more readable. </details></td></tr> <tr><td><details> <summary><strong> How to enable\disable automation</strong></summary><hr> - When you first install PR-Agent app, the [default mode](https://github.com/Codium-ai/pr-agent/blob/main/Usage.md#github-app-automatic-tools) for the `review` tool is: ``` pr_commands = ["/review", ...] ``` meaning the `review` tool will run automatically on every PR, with the default configuration. Edit this field to enable/disable the tool, or to change the used configurations </details></td></tr> <tr><td><details> <summary><strong> Auto-labels</strong></summary><hr> The `review` tool can auto-generate two specific types of labels for a PR: - a `possible security issue` label, that detects possible [security issues](https://github.com/Codium-ai/pr-agent/blob/tr/user_description/pr_agent/settings/pr_reviewer_prompts.toml#L136) (`enable_review_labels_security` flag) - a `Review effort [1-5]: x` label, where x is the estimated effort to review the PR (`enable_review_labels_effort` flag) </details></td></tr> <tr><td><details> <summary><strong> Extra sub-tools</strong></summary><hr> The `review` tool provides a collection of possible feedbacks about a PR. It is recommended to review the [possible options](https://github.com/Codium-ai/pr-agent/blob/main/docs/REVIEW.md#enabledisable-features), and choose the ones relevant for your use case. Some of the feature that are disabled by default are quite useful, and should be considered for enabling. For example: `require_score_review`, `require_soc2_ticket`, and more. </details></td></tr> <tr><td><details> <summary><strong> More PR-Agent commands</strong></summary><hr> > To invoke the PR-Agent, add a comment using one of the following commands: > - **/review**: Request a review of your Pull Request. > - **/describe**: Update the PR title and description based on the contents of the PR. > - **/improve [--extended]**: Suggest code improvements. Extended mode provides a higher quality feedback. > - **/ask \<QUESTION\>**: Ask a question about the PR. > - **/update_changelog**: Update the changelog based on the PR's contents. > - **/add_docs** 💎: Generate docstring for new components introduced in the PR. > - **/generate_labels** 💎: Generate labels for the PR based on the PR's contents. > - **/analyze** 💎: Automatically analyzes the PR, and presents changes walkthrough for each component. >See the [tools guide](https://github.com/Codium-ai/pr-agent/blob/main/docs/TOOLS_GUIDE.md) for more details. >To list the possible configuration parameters, add a **/config** comment. </details></td></tr> </table> See the [review usage](https://github.com/Codium-ai/pr-agent/blob/main/docs/REVIEW.md) page for a comprehensive guide on using this tool. </details> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/codiumai-pr-agent[bot]"><img src="https://avatars.githubusercontent.com/in/354216?v=4" />codiumai-pr-agent[bot]</a> commented <strong> 3 months ago</strong> </div> <div class="markdown-body"> <h2>PR Code Suggestions</h2> <table><thead><tr><th></th><th>Suggestions </th></tr></thead><tbody><tr><td><strong>best practice</strong></td><td><table><tr><td> <details><summary>Use <code>const</code> for keys that are not modified. </summary> ___ **Consider using `const` for the keys that are not going to be modified. This can improve <br> readability and maintainability of the code.** [windows/universal_ble_plugin.cpp [30-35]](https://github.com/Navideck/universal_ble/pull/4/files#diff-d20f69f92c5b381b134f30879fa256f148268e1370657df72f5db418ae03c6e0R30-R35) ```diff -auto isConnectableKey = L"System.Devices.Aep.Bluetooth.Le.IsConnectable"; -auto isConnectedKey = L"System.Devices.Aep.IsConnected"; -auto isPairedKey = L"System.Devices.Aep.IsPaired"; -auto isPresentKey = L"System.Devices.Aep.IsPresent"; -auto deviceAddressKey = L"System.Devices.Aep.DeviceAddress"; -auto signalStrengthKey = L"System.Devices.Aep.SignalStrength"; +const auto isConnectableKey = L"System.Devices.Aep.Bluetooth.Le.IsConnectable"; +const auto isConnectedKey = L"System.Devices.Aep.IsConnected"; +const auto isPairedKey = L"System.Devices.Aep.IsPaired"; +const auto isPresentKey = L"System.Devices.Aep.IsPresent"; +const auto deviceAddressKey = L"System.Devices.Aep.DeviceAddress"; +const auto signalStrengthKey = L"System.Devices.Aep.SignalStrength"; ``` </details></td></tr><tr><td> <details><summary>Handle exceptions more specifically. </summary> ___ **Consider handling exceptions more specifically rather than using a general catch-all. This <br> can help with debugging and understanding what kind of exceptions can occur.** [windows/universal_ble_plugin.cpp [555-574]](https://github.com/Navideck/universal_ble/pull/4/files#diff-d20f69f92c5b381b134f30879fa256f148268e1370657df72f5db418ae03c6e0R555-R574) ```diff try { ... } -catch (...) +catch (const std::exception& e) { - std::cout << "Error in parsing manufacturer data: " << deviceId << std::endl; + std::cout << "Error in parsing manufacturer data: " << deviceId << " Exception: " << e.what() << std::endl; return std::vector<uint8_t>(); } ``` </details></td></tr><tr><td> <details><summary>Use more descriptive variable names. </summary> ___ **Consider using a more descriptive variable name than `_scanResult`. This can improve `<br> `readability `<br> `and `<br> `maintainability `<br> `of `<br> `the `<br> `code.** [windows/universal_ble_plugin.cpp [607]](https://github.com/Navideck/universal_ble/pull/4/files#diff-d20f69f92c5b381b134f30879fa256f148268e1370657df72f5db418ae03c6e0R607-R607) ```diff -auto _scanResult = scanResults.at(scanResult.device_id()); +auto existingScanResult = scanResults.at(scanResult.device_id()); ``` </details></td></tr><tr><td> <details><summary>Remove commented-out code or explain why it's there. </summary> ___ **Consider removing the commented-out code or add a comment to explain why it's commented <br> out. This can improve readability and maintainability of the code.** [windows/universal_ble_plugin.cpp [636-639]](https://github.com/Navideck/universal_ble/pull/4/files#diff-d20f69f92c5b381b134f30879fa256f148268e1370657df72f5db418ae03c6e0R636-R639) ```diff -// if nothing to update then return -// if (!shouldUpdate) -// { -// return; -// } +// Removed commented-out code ``` </details></td></tr></table></td></tr></tr></tbody></table><hr> <details> <summary><strong>✨ Usage guide:</strong></summary><hr> **Overview:** The `improve` tool scans the PR code changes, and automatically generates suggestions for improving the PR code. The tool can be triggered [automatically](https://github.com/Codium-ai/pr-agent/blob/main/Usage.md#github-app-automatic-tools) every time a new PR is opened, or can be invoked manually by commenting on a PR. When commenting, to edit [configurations](https://github.com/Codium-ai/pr-agent/blob/main/pr_agent/settings/configuration.toml#L69) related to the improve tool (`pr_code_suggestions` section), use the following template: ``` /improve --pr_code_suggestions.some_config1=... --pr_code_suggestions.some_config2=... ``` With a [configuration file](https://github.com/Codium-ai/pr-agent/blob/main/Usage.md#working-with-github-app), use the following template: ``` [pr_code_suggestions] some_config1=... some_config2=... ``` <table><tr><td><details> <summary><strong> Enabling\disabling automation </strong></summary><hr> When you first install the app, the [default mode](https://github.com/Codium-ai/pr-agent/blob/main/Usage.md#github-app-automatic-tools) for the improve tool is: ``` pr_commands = ["/improve --pr_code_suggestions.summarize=true", ...] ``` meaning the `improve` tool will run automatically on every PR, with summarization enabled. Delete this line to disable the tool from running automatically. </details></td></tr> <tr><td><details> <summary><strong> Utilizing extra instructions</strong></summary><hr> Extra instructions are very important for the `improve` tool, since they enable to guide the model to suggestions that are more relevant to the specific needs of the project. Be specific, clear, and concise in the instructions. With extra instructions, you are the prompter. Specify relevant aspects that you want the model to focus on. Examples for extra instructions: ``` [pr_code_suggestions] # /improve # extra_instructions=""" Emphasize the following aspects: - Does the code logic cover relevant edge cases? - Is the code logic clear and easy to understand? - Is the code logic efficient? ... """ ``` Use triple quotes to write multi-line instructions. Use bullet points to make the instructions more readable. </details></td></tr> <tr><td><details> <summary><strong> A note on code suggestions quality</strong></summary><hr> - While the current AI for code is getting better and better (GPT-4), it's not flawless. Not all the suggestions will be perfect, and a user should not accept all of them automatically. - Suggestions are not meant to be simplistic. Instead, they aim to give deep feedback and raise questions, ideas and thoughts to the user, who can then use his judgment, experience, and understanding of the code base. - Recommended to use the 'extra_instructions' field to guide the model to suggestions that are more relevant to the specific needs of the project, or use the [custom suggestions :gem:](https://github.com/Codium-ai/pr-agent/blob/main/docs/CUSTOM_SUGGESTIONS.md) tool - With large PRs, best quality will be obtained by using 'improve --extended' mode. </details></td></tr> <tr><td><details> <summary><strong> More PR-Agent commands</strong></summary><hr> > To invoke the PR-Agent, add a comment using one of the following commands: > - **/review**: Request a review of your Pull Request. > - **/describe**: Update the PR title and description based on the contents of the PR. > - **/improve [--extended]**: Suggest code improvements. Extended mode provides a higher quality feedback. > - **/ask \<QUESTION\>**: Ask a question about the PR. > - **/update_changelog**: Update the changelog based on the PR's contents. > - **/add_docs** 💎: Generate docstring for new components introduced in the PR. > - **/generate_labels** 💎: Generate labels for the PR based on the PR's contents. > - **/analyze** 💎: Automatically analyzes the PR, and presents changes walkthrough for each component. >See the [tools guide](https://github.com/Codium-ai/pr-agent/blob/main/docs/TOOLS_GUIDE.md) for more details. >To list the possible configuration parameters, add a **/config** comment. </details></td></tr> </table> See the [improve usage](https://github.com/Codium-ai/pr-agent/blob/main/docs/IMPROVE.md) page for a more comprehensive guide on using this tool. </details> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/fotiDim"><img src="https://avatars.githubusercontent.com/u/2326415?v=4" />fotiDim</a> commented <strong> 3 months ago</strong> </div> <div class="markdown-body"> <p>/review</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/codiumai-pr-agent[bot]"><img src="https://avatars.githubusercontent.com/in/354216?v=4" />codiumai-pr-agent[bot]</a> commented <strong> 3 months ago</strong> </div> <div class="markdown-body"> <p><strong><a href="https://github.com/Navideck/universal_ble/pull/4#issuecomment-1918584440">Persistent review</a></strong> updated to latest commit <a href="https://github.com/Navideck/universal_ble/commit/a47f20fa6af38c0f265b5805ecb52ae4462d2a61">https://github.com/Navideck/universal_ble/commit/a47f20fa6af38c0f265b5805ecb52ae4462d2a61</a></p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/fotiDim"><img src="https://avatars.githubusercontent.com/u/2326415?v=4" />fotiDim</a> commented <strong> 3 months ago</strong> </div> <div class="markdown-body"> <p>/describe</p> </div> </div> <div class="comment"> <div class="user"> <a rel="noreferrer nofollow" target="_blank" href="https://github.com/codiumai-pr-agent[bot]"><img src="https://avatars.githubusercontent.com/in/354216?v=4" />codiumai-pr-agent[bot]</a> commented <strong> 3 months ago</strong> </div> <div class="markdown-body"> <p><strong><a href="https://github.com/Navideck/universal_ble/pull/4">PR Description</a></strong> updated to latest commit (<a href="https://github.com/Navideck/universal_ble/commit/a47f20fa6af38c0f265b5805ecb52ae4462d2a61">https://github.com/Navideck/universal_ble/commit/a47f20fa6af38c0f265b5805ecb52ae4462d2a61</a>)</p> </div> </div> <div class="page-bar-simple"> </div> <div class="footer"> <ul class="body"> <li>© <script> document.write(new Date().getFullYear()) </script> Githubissues.</li> <li>Githubissues is a development platform for aggregating issues.</li> </ul> </div> <script src="https://cdn.jsdelivr.net/npm/jquery@3.5.1/dist/jquery.min.js"></script> <script src="/githubissues/assets/js.js"></script> <script src="/githubissues/assets/markdown.js"></script> <script src="https://cdn.jsdelivr.net/gh/highlightjs/cdn-release@11.4.0/build/highlight.min.js"></script> <script src="https://cdn.jsdelivr.net/gh/highlightjs/cdn-release@11.4.0/build/languages/go.min.js"></script> <script> hljs.highlightAll(); </script> </body> </html>

Navideck / universal_ble