Add Extensive Logging
Description
- Integrate Pulse and set it up using SwiftLog Logging System
- Add a "bolt" button to "Experimental Features". Tap it five times, and it'll show a new "Super Experimental Features" section.
- Show "Extensive Logging" flag in the new section. When you enable it, it'll show a warning alert.
- Add "Logger" section in "App Settings" (if enabled)
📲 You can test the changes from this Pull Request in WordPress by scanning the QR code below to install the corresponding build.
| App Name | WordPress | |
| Configuration | Release-Alpha | |
| Build Number | 30061 | |
| Version | PR #25005 | |
| Bundle ID | org.wordpress.alpha | |
| Commit | e164a07306a6475639f7c8d0324e9b75da6d19d4 | |
| Installation URL | 6soibd37sjcbg |
📲 You can test the changes from this Pull Request in Jetpack by scanning the QR code below to install the corresponding build.
| App Name | Jetpack | |
| Configuration | Release-Alpha | |
| Build Number | 30061 | |
| Version | PR #25005 | |
| Bundle ID | com.jetpack.alpha | |
| Commit | e164a07306a6475639f7c8d0324e9b75da6d19d4 | |
| Installation URL | 0f72lfs8bc7f0 |
Version 26.5 has now entered code-freeze, so the milestone of this PR has been updated to 26.6.
Renamed it to "Developer Tools"
If I understand correctly, with the changes in this PR, the app now always uses Pulse to log HTTP requests and responses, and the feature toggle controls whether the user can see those logs. Considering 99% of the users won't turn on the feature toggle and view the logs, to avoid running code and taking up the app's memory for nothing, should we change the model to only log HTTP requests when the feature toggle is on?
should we change the model to only log HTTP requests when the feature toggle is on?
There is a significant impact on performance and app on-disk see. If has to be a debug-only feature.
Quality Gate passed
Issues
5 New issues
0 Accepted issues
Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code