Defining custom or complex views

Abierto
#2,357 2 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
Bastante claro
Estado de actividad
Activo
Stack tecnológico
go
Área
backend

Línea de trabajo

Read the related issues #1212 and #1628, then investigate how view rendering handles filter conditions and whether SysML expressions can express the requested interface, its ends, and ancestors up to a common ancestor. The issue does not name implementation files or tests, so first locate the view and filter entry points; done means demonstrating a SysML-only custom view or documenting why a custom Go view type is needed.

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

Descripción

This is somewhat related to https://github.com/Open-MBEE/OpenSysML/issues/1212 and https://github.com/Open-MBEE/OpenSysML/issues/1628 , but in context of rendering views.

I tried to make a custom view definition. Its main purpose is given an interface to render that interface together with its ends and all of the ancestors up to a common one.

I tried to do that using filter conditions with no luck yet.

The spec says that

A filter condition is a Boolean valued,
model-level evaluable expression (see [KerML. 7.4.9]) declared using the keyword filter followed by a
Boolean-valued, model-level evaluable expression (see [KerML. 7.4.9]).

Seemingly, that must be enough, but diving deeper, it appears that I couldn't use calc usages or defs, and it looks like complex filters are cubersome at least and impossible at most..

How to make such custom view? In the worst case I could rely on go api and make custom view type, but still am I missing something with sticking only to sysml? It seems that sysml must be flexible enough to make such representations out of the box.

Lenguaje dominante
Go
Estrellas
59
Forks
20
Merge medio
10 h 52 min
PR fusionados (30 d)
903

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.