[#110] Add Player build report example queries matching Project Auditor views#111
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a set of reproducible “Project Auditor Build view → SQLite query” examples for Player build reports, and introduces small schema enhancements to make the documented groupings easy and performant.
Changes:
- Added a new documentation page with short, UI-mirroring queries (including example output) for common BuildReport analyses.
- Extended the BuildReport PackedAssets schema to expose
asset_nameandasset_extensionfor convenient grouping in SQL. - Added/extended tests and test data to pin the documented example outputs and validate the new derived columns.
Reviewed changes
Copilot reviewed 7 out of 9 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| UnityDataTool.Tests/BuildReportTests.cs | Adds assertions for asset_name/asset_extension and a new Happy Harvest regression test that pins documented query outputs. |
| TestCommon/Data/BuildReports/README.md | Documents the new happyHarvest.buildreport test fixture and its purpose. |
| Documentation/buildreport.md | Adds a cross-link to the new Player build report example queries and documents the new derived columns. |
| Documentation/analyze-examples.md | Adds a cross-link to the new BuildReport-focused examples page. |
| Documentation/analyze-examples-buildreport.md | New doc page mapping Project Auditor Build views to equivalent SQLite queries with real output snippets. |
| Analyzer/SQLite/Handlers/PackedAssetsHandler.cs | Computes and inserts asset_name / asset_extension derived from build_time_asset_path during import. |
| Analyzer/Resources/PackedAssets.sql | Adds asset_name / asset_extension columns to build_report_source_assets and exposes them via build_report_packed_asset_contents_view. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
SkowronskiAndrew
force-pushed
the
issue110
branch
from
July 23, 2026 22:06
851771a to
0d6379c
Compare
Update AGENTS.md so that this happens more reliably in future edits.
Collaborator
Author
|
I'll put this in now so that the new page goes live, we may do some small updates based on further testing. |
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.
Summary
Fixes #110.
The Project Auditor package has useful views of BuildReport data (build summary, size by runtime type, and objects grouped by source asset, file extension, build file, etc.), but they do not scale well to very large builds and only cover the last Player build. UnityDataTool already imports the same raw BuildReport data into SQLite, which handles millions of objects and any number of past reports — but SQL is less approachable than a built-in UI. This PR bridges that gap with a documentation page that maps each Project Auditor Build view to an equivalent short query, with real example output, and adds a small schema addition where plain SQL would have been awkward.
Changes
Documentation
Documentation/analyze-examples-buildreport.md(following theanalyze-examples-contentlayout.mdnaming convention): each Project Auditor Build view mapped to a query with genuine output snippets, including group-by/drill-down query pairs mirroring the UI's collapsed/expanded grouping. Includes one Project Auditor screenshot to anchor the mapping.TestCommon/Data/BuildReports/happyHarvest.buildreportso the output is reproducible; it also gives the tests a larger 6.6 report with a ContentSummary and diverse content.buildreport.mdandanalyze-examples.md.Schema
build_report_source_assetsgainsasset_name(filename without extension) andasset_extension(lower-cased, without the dot) columns, computed inPackedAssetsHandlerbecause extracting them in SQLite SQL is awkward. Both are exposed bybuild_report_packed_asset_contents_view, making all the documented groupings one-lineGROUP BYqueries.Testing
dotnet test— full suite green (761 passed, 10 skipped, pre-existing platform skips).Analyze_BuildReport_HappyHarvest_MatchesDocumentedExamplestest pins the example numbers shown in the documentation (including that the PackedAssets per-type totals match the ContentSummary).asset_name/asset_extensionin the existing PackedAssets test.