Unity-Technologies / Unity-Technologies/UnityDataTools
Support Unity 6.7 content directory analysis (ContentLayout.json v3)
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 821
- Forks
- 71
- Avg merge
- 3h 13m
- Merged PRs (30d)
- 9
Description
The schema of ContentLayout.json is changing between Unity 6.6 and 6.7 which breaks the ability to fully analyze content directory builds generated by Unity 6.7.
We need to update the support and try to maintain support for Unity 6.6 builds (the v2 schema). One approach might be to translate v2 to v3 files, and then only have support for importing the v3 data structures, this should be technically feasible because the changes only remove and reorganize data, no new data is added.
As part of this work https://github.com/Unity-Technologies/UnityDataTools/blob/main/Documentation/contentlayout.md should be reviewed to make sure it is accurate for both 6.6 and 6.7.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing ContentLayout.json import and analysis path, comparing the Unity 6.6 v2 and 6.7 v3 schemas described in the issue. Then review Documentation/contentlayout.md for accuracy across both versions; done means 6.7 content directory builds are fully analyzable while 6.6 v2 builds remain supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, unity
- Domain
- documentation, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100