det: JSON GENERATE / JSON PARSE not modelled (census #7709, 2 programs)

Abierto
#7,524 16 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
18/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
python
Área
devtools

Línea de trabajo

The survey lives in cics_census.py, run as survey --out DIR --label before with CICS_CENSUS_CORPORA set, then blockers DIR --label before reports the gap. The issue gives no file or test for the JSON GENERATE/PARSE translator, so first find where the det translator handles statement families and how it marks one as not modelled. Done would mean the census reports these statements as modelled, but the issue does not define that criterion or name a burned-estate corpus to check against.

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

Descripción

claim:melek scope:core

Census breadth survey (#5052, main d86d5eabb): 2 non-burned CICS programs (of 21 surveyed) hit this gap, counts only; no census code was read (mainframe-evidence-policy 3).

Gap family: JSON GENERATE / JSON PARSE

Det translator status: not modelled / refused. Burned-estate programs affected: 0. None of these alone makes a non-burned program whole (other gap classes remain), so rank by program count only.

Class / Sibling gaps

Class: det-translator statement families the census surveys report as "not modelled" in CICS programs. Siblings are the other rows in the #5052 ranking comment (STRING, JSON GENERATE/PARSE, EXEC CICS WEB, MOVE single-byte literal, EXEC SQL ROLLBACK in CICS); each has its own issue. Work only from burned estates (case work on non-burned repos is out of scope).

Reproduce: cics_census.py survey --out DIR --label before with CICS_CENSUS_CORPORA, then blockers DIR --label before.

Slices (census #7709, owner reopen 2026-11-05)

Work from IBM's definition on fixtures / cics-crucible only; never census source (#7709 rule 2).

  • JSON GENERATE: translate from the IBM definition (name matching, NAME / SUPPRESS / COUNT, JSON-CODE, ON EXCEPTION) on a fixture; register entry marks it oracle-unbacked (no L2+ claim)
  • JSON PARSE: same, on a fixture (name matching, CONVERTING / WITH DETAIL, JSON-STATUS, ON EXCEPTION)
  • Re-survey: the 2 census JSON rows are gone; post the count on #7709
Lenguaje dominante
Python
Estrellas
57
Forks
11
Merge medio
1 h 35 min
PR fusionados (30 d)
975

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 squid-protocol/gitgalaxy

Todos los issues de squid-protocol/gitgalaxy

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.