Repository navigation
Document the problem_specifications_slug key - #600
keiravillekode wants to merge 1 commit into
Conversation
A track sometimes needs a different slug from the problem-specifications exercise it implements, for example to avoid a name collision in the track's language. See exercism/configlet#936
|
I used Claude for this docs change. |
|
@keiravillekode Is this ready for review? |
|
Something occurred to me while reviewing: at what point does the exercise author know there is a name conflict. Presumably after using What if the name conflict is already known? Is it worthwhile thinking about adding some functionality to |
|
We have 4 known use cases: factor We did not know about the conflict until after the exercises had been merged. Users noticed that the tests were either not being run (factor) or were timing out when run through the web app even though they passed locally (haskell). |
|
Given that these are edge cases and this route should only be used as a last resort, I think it's fine to not expose it via the create command. |
|
I'm considering using this for |
Yes. If we rename the existing exercise, students can end up with their old solution file plus the new stub file, and it isn't obvious how to get rid of the old solution file. Example deprecating the existing one: Haskell PR 1320 Note than
|
A track sometimes needs a different slug from the problem-specifications exercise it implements, for example to avoid a name collision in the track's language.
See exercism/configlet#936