Integration of extensions

Abierto
#273 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
python
Área
backend-api-design

Línea de trabajo

Start by reading PEtab v2 extensions in PR #537, then review the current PEtab validator and petab.Problem API mentioned in the issue. Compare direct incorporation with a pluggy-based mechanism, including how extensions might interact. Done means documenting and implementing an agreed extension integration design.

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

Descripción

With PEtab v2 we will introduce extensions to PEtab that will add new functionality. (In exceptional cases, extensions might also change some existing rules, but this is for another issue). For example, there is petab-select for model selection, units support for PEtab, and there were discussions to move the petab v1 visualization functionality to an extension.

Ideally, those extensions would be able to extend the current PEtab validator. Possibly they would also want to extend the petab.Problem API. Not sure what else.

The question is, whether those extensions should be directly incorporated here in libpetab, or whether we provide some plugin mechanism (via pluggy?). Currently, I'd prefer the latter, to avoid bloating this library and allow for mostly independent development of the extensions. However, this might make it difficult to handle any interaction of extensions. Happy to discuss other options and relevant points for plugins to modify libpetab behaviour.

Lenguaje dominante
Python
Estrellas
18
Forks
9
Sin PR fusionados en 30 d

Guía de contribución

Abrir la guía de contribución

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 PEtab-dev/libpetab-python

Todos los issues de PEtab-dev/libpetab-python

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.