Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#331 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
csharp
Área
build-system, developer-experience

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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)
Lenguaje dominante
C#
Estrellas
1
Forks
1
Merge medio
1 h 57 min
PR fusionados (30 d)
36

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de MASS4ORG/Turian

Todos los issues de MASS4ORG/Turian

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.