Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Extract stable type identity into a shared library for engine, graphs and DataAssets

Aperta
  • Qualcosa non va?
#331 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
csharp
Ambito
build-system, developer-experience

Direzione di ricerca

Start by reading the engine’s TypeRegistry and alias map, then compare them with MASS4ORG/Graph’s StableId and IdentityRegistry; the issue does not name source files or tests. The work is an owner-gated extraction into a separate repository, coordinated with the serialization branch, Graph#7, and #55. Done means all three layers use the library, existing serialized TypeIds still load, and the documented contract covers canonical text, renames, and cycle rejection.

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

Descrizione

c:engine p:medium sit:waiting size:L t:refactor
Current State

The engine resolves serialized types through a static TypeRegistry keyed by [TypeId] GUIDs, with an alias map for renamed types and assembly scanning to bind GUIDs to CLR types. The node-graph library (MASS4ORG/Graph) needs the same identity concept for node, port and trigger types and currently carries its own StableId/IdentityRegistry with rename chains. The DataAsset-driven design layer (#55) is growing identity needs of its own. Three separate identity registries would recreate the string-identity problem in a new form: the same asset would need different identities depending on which subsystem reads it.

This issue extracts the shared part into a small general library that all three consume. It is owner-gated: it runs as a separate PR in its own worktree, sequenced against the in-flight serialization branch, and no other engine change rides along.

Tasks:
  • Create the identity library in its own repository: opaque stable identities, a registry and a rename map, nothing more (no reflection, no CLR binding, no serialization)
  • Keep assembly scanning and CLR type binding in the engine, layered over the library
  • Move the engine's alias map onto the library's rename map
  • Replace the graph library's internal identity types with the extracted library (MASS4ORG/Graph#7)
  • Agree with the DataAsset-driven design work (#55) that its identities use the same library
  • Document the identity contract (canonical text form, rename semantics, cycle rejection)
Acceptance Criteria:
  • Serialized TypeIds are unchanged; existing scenes, assets and aliases load as before
  • The library depends on nothing beyond the base class library and is trimming- and AOT-safe
  • The engine, the graph library and the DataAsset layer resolve identities through the same library
  • The PR contains only the extraction and its adoption
Related:
  • #55 (DataAsset-driven design: co-stakeholder for identity)
  • #63 (identity types evaluated without changing serialized IDs)
  • MASS4ORG/Graph#1 (graph core), MASS4ORG/Graph#7 (graph identity registry)
Lingua principale
C#
Stelle
1
Fork
1
Merge medio
1h 57m
PR unite (30g)
36

Preparare l'ambiente

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 MASS4ORG/Turian

Tutte le issue di MASS4ORG/Turian

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.