aclai-lab / aclai-lab/SoleLogics.jl
SoleData.jl dependency
- Lenguaje dominante
- Julia
- Estrellas
- 20
- Forks
- 7
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
At the moment of writing, we have a `SoleData.jl` weak dependency due to the following test:
https://github.com/aclai-lab/SoleLogics.jl/blob/68560e8d58426fce547b13b90ec7e3619b822267/test/interpretation-sets.jl#L18-L28
Unfortunately, this becomes an ugly, circular dependency requiring to release a new version of `SoleData.jl` updating the `SoleLogics.jl` version in `Project.toml` each time we want to release a new version of `SoleLogics.jl`; otherwise, tests will fail.
Hence, my question is: can we test this functionality some other way? (e.g., using another subtype of `AbtractInterpretationSet`)
Or else, can this test be moved to `SoleData.jl` tests?
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Línea de trabajo
Start with `test/interpretation-sets.jl` (linked lines 18–28) to inspect the exact `SoleData.jl`-dependent test. Then inspect this repo’s `Project.toml` and the test/package layout to confirm how the version coupling is introduced. Check `SoleData.jl`’s test suite for a comparable `AbstractInterpretationSet`-based case to relocate the test if needed. Done means the test passes without creating a release-version circular dependency between the two packages.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- julia
- Área
- testing-qa
- Tipo de issue
- Refactorización
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 35/100