I noticed that the website now has overview pages for individual exercises, showing in which track / language we could solve them in. Really cool! :)
Could we also get this as an API endpoint so this information can be used for tooling? Sometimes I would like to tell my editor plugin to start an exercise by first selecting an exercise and then choosing a track instead of starting with a track and then selecting an exercise.
I’m aware that I can get the info already with the current, but the solution used by @keiraville is not very useful for an editor plugin.
My approach would be to query all tracks via https://exercism.org/api/v2/tracks/$TRACK/exercises, but then I’d have to cache those results somehow as to not hammer the API and to have a quick response time for the plugin.
If it turns this feature is not wort the effort to implement and support it then I’m fine with using the approach I mentioned above, but I’d assume if we make it easier to get from exercise to course then more people will build and use that way of exploring Exercism.
As long as a track doesn’t have it already implemented as a practice exercise. That was the problem on the Julia track recently where they wanted to redo leap as a concept exercise instead of a practice exercise. Even if it’s deprecated, you can’t remove the earlier exercise and you can’t have the same slug twice in a track.
So hypothetically yeah, a practice exercise could be a concept exercise elsewhere. I’m not aware of a scenario like that though. I think it’d still be worthwhile to track.