aclai-lab / aclai-lab/SoleLogics.jl
SoleData.jl dependency
- Langage dominant
- Julia
- Étoiles
- 20
- Forks
- 7
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
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?
Guide de contribution
Aucun guide de contribution indexé pour ce dépôt
Piste de recherche
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.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- julia
- Domaine
- testing-qa
- Type d'issue
- Refactorisation
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 35/100