analyze: support ContentLayout.json v4 (Unity 7000.0)

Aperta
#159 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
csharp, unity
Ambito
backend, data

Direzione di ricerca

Start with ContentLayoutParser and Documentation/contentlayout-database.md, then inspect the v2 and v3 reference layouts and automated tests. Accept schema version 4 while preserving versions 2 and 3; derive the built-in flag from StableId source type 5 and check that built-in references resolve. Add a v4 layout fixture and verify the documented StableId representation.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Unity 7000.0 (current trunk) writes ContentLayout.json schema version 4. analyze supports versions 2 and 3, so it rejects the file:

Unsupported ContentLayout.json version 4 (this version of UnityDataTool supports versions 2 and 3).
Failed to process: ContentLayout.json

The content files are still analyzed (once SerializedFile v27 is supported), but without the layout. References between content files can't be resolved, and source-asset information is missing.

Schema change (v3 -> v4)

Unity's description of the change:

StableId content changed from the one-way identity hash to the source tuple string it derived from, "cfid-<guid>-<lfid>-<sourceTypeInt>" - identical to the external-reference pathNames written into built content files, so the two are cross-referenceable by string equality. The built-in entry is an ordinary tuple entry of source type DefaultResources, and ArtifactIndex replaced ContentHash.

In practice the JSON keys are the same as v3. The differences:

  • SerializedFiles[].StableId is now e.g. cfid-78532141fd7679a458405eb16bdb75fd-0-1 instead of a bare hash. It matches the external reference paths in the .cf files exactly, as shown by serialized-file externalrefs.
  • IsBuiltIn is gone. The built-in "unity default resources" entry is now cfid-0000000000000000e000000000000000-0-5, with source type 5 = DefaultResources.

Quick experiment

I accepted version 4 in ContentLayoutParser and deserialized it as the v3 model. With that, analyze imported the layout and resolved the cross-file references, since those are resolved by position in the dependency list rather than by StableId. One gap remained: the built-in entry is no longer flagged as built-in, so scene references to default resources (e.g. m_SpotCookie) ended up in dangling_refs. The filename column in content_layout_serialized_files_view also no longer shows the built-in path.

Work includes

  • Accept version 4 and keep supporting 2 and 3.
  • Derive is_builtin for v4 from the source type in the StableId (5 = DefaultResources), and make sure references to built-in files resolve as they did with v3.
  • Decide how to present stable_id: keep the tuple string, or also split it into guid / lfid / source type columns. Since StableId now equals the external reference path, it could also be used to cross-check the positional resolution.
  • Add a v4 reference layout for automated tests, e.g. from a 7000.0 rebuild of UnityProjects/LeadingEdge.
  • Update Documentation/contentlayout-database.md and any docs describing StableId.
Lingua principale
C#
Stelle
841
Fork
75
Merge medio
1g 7h
PR unite (30g)
3

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Unity-Technologies/UnityDataTools

Tutte le issue di Unity-Technologies/UnityDataTools

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.