Generate nested PowerShell class property schemas with cycle-safe references

Abierto
#1,813 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
12/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
json, powershell, rust
Área
tooling

Línea de trabajo

This is design work spanning both schema adapters, type resolution for module-defined and .NET types, and cycle detection for recursive classes, so it is not a first-timer task. Start by reading the follow-up context in #1775 and the existing class-property schema handling in the PowerShell adapter. Done would mean a settled design for $defs/$ref generation, agreed handling of inheritance and unknown types, and tests for nested, array, inherited and recursive cases.

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

Descripción

Issue-Enhancement Needs Triage
Summary of the new feature / enhancement

Follow-up to #1775: module-defined class properties are recognized as objects, but their nested members are not constrained. Generate nested schemas so DSC and authoring tools can validate embedded resource data.

Proposed technical implementation details (optional)

Generate reusable $defs and $ref entries for class types, with cycle detection for recursive classes and consistent inherited-member handling in both adapters. Preserve explicit nullability and array item constraints. Determine which nested members are configurable rather than assuming every nested member has a DscProperty attribute. Extend type resolution to classes and enums declared in other module files or exposed by .NET where metadata is available; unknown types must remain explicitly documented. Cover nested objects, arrays, inheritance, and recursive definitions.

Lenguaje dominante
Rust
Estrellas
545
Forks
82
Merge medio
4 d 16 h
PR fusionados (30 d)
21

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

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 PowerShell/DSC

Todos los issues de PowerShell/DSC

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.