Query: expose the verify link, connection/attachment properties, and TransitionUsage rows

Abierto
#2,340 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
28/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
go

Línea de trabajo

Start with the query property implementation and wire-contract list, then read the query tests and api.md around add_verify. Trace how the grammar builds TransitionUsage and how the index turns it into an ActionUsage; probe the existing connector and port model to find their relationship facts. Done means verification, port graph, and transition rows are queryable, with the stated fixtures and unknown-property refusals passing.

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

Descripción

Disclaimer, this issue was detected and written by an AI

Summary

Three relationship facts are in the model but not in the query substrate, so the
cross-view warnings and the M5 cyclomatic metric cannot be projections:

  1. verify link — satisfiedRequirement/satisfyingFeature cover satisfy;
    a verification case's verify objective has no queryable property, so the
    verifier half of the consistency check is engine-capable-blocked.
  2. connection/attachment — a port graph (which connector/attachment reaches
    a port) is not queryable, so the port-mismatch warning bucket is not a
    predicate.
  3. TransitionUsage rows — a transition answers no row of its own; it is an
    anonymous ActionUsage, so per-machine E − N + 2P cannot be computed from
    the same answer. Probed at 0.12.1: a fixture with
    transition t1 first a if true then b; answers 6 rows — Package,
    StateDefinition, StateUsage ×3, ActionUsage ×1 — and no
    TransitionUsage.

Proposal

  • Add the verify analogue of the satisfy pair. Suggested names after a probe:
    verifiedRequirement (the requirement a verify membership names) and
    verifyingCase (the verification case whose objective holds it), each absent
    when unresolved or not a verify membership. add_verify already writes the
    membership (api.md:192), so the relationship is expressible.
  • Add connection/attachment properties, named after the metamodel fact they
    report (probe first): e.g. a connection/attachment property on a connector
    usage and the reaching connector(s) on a port usage, or a pair of endpoint
    properties. Whatever the names, make the port graph answerable in one scoped
    query without a per-element GetSymbol fan-out.
  • Make a transition answer a row: @type=TransitionUsage, with @id, owner,
    name, and its source/target (or the succession ends as properties). The
    grammar already builds TransitionUsages; the index/query answer must stop
    flattening them into an anonymous ActionUsage.

Tests

  • A state-machine fixture: TransitionUsage rows count and owner; the same
    E − N + 2P derivation the metric would use.
  • A verification fixture: verify Req; inside a case's objective answers
    verifiedRequirement/verifyingCase; a satisfy stays on the existing pair.
  • A connector/port fixture: the port graph is answerable and the mismatch
    predicate can be written without a lookup per element.
  • Keep unknown property refusals for names outside the grown set.

Acceptance

  • The verifier half and the port-graph bucket are query predicates.
  • A transition is its own row with identity and owner.
  • Wire-contract list and query tests move together.
Lenguaje dominante
Go
Estrellas
59
Forks
20
Merge medio
10 h 23 min
PR fusionados (30 d)
897

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 Open-MBEE/OpenSysML

Todos los issues de Open-MBEE/OpenSysML

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.