Support Unity 6.7 content directory analysis (ContentLayout.json v3)

Open
#131 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp, unity

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.

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.

Dominant language
C#
Stars
821
Forks
71
Avg merge
3h 13m
Merged PRs (30d)
9

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Unity-Technologies/UnityDataTools

All issues in Unity-Technologies/UnityDataTools

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.