Add missing descriptions to 17 artifacts#1685
Merged
Merged
Conversation
Fill in empty/absent "description" fields in the __artifacts_v2__ block for 17 iOS artifacts. Descriptions are derived from each artifact's actual paths/queries/columns and describe what the parser extracts and its source. Also add a broad-exception-caught pragma to fmfdDevices' existing per-file resilience catch so the now-touched file lints at 10.00 (no behavior change). Artifacts: AWESearch, appleMapsApplication, appleMapsGroup, appleMapsSearchHistory, audiTripdata, bluetoothOther, bluetoothPairedLE, bluetoothPairedReg, cacheRoutesGmap, carCD, cashApp, cashAppB, draftmessage, fmfdDevices, tileAppNetDb, weatherAppLocations, webClips.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What
Fills in empty or absent `description` fields in the `artifacts_v2` metadata block for 17 iOS artifacts. The `description` renders in the artifact's HTML report header and is carried into LAVA, so these previously showed no explanation of what the artifact does.
Each description was written from the artifact's actual paths, SQL query and output columns (not guessed), following the existing house style ("Parses X from Y").
Notes