Closed nywilken closed 6 years ago
Is there an impact to the server structure of Exercism if we swap out UUIDs for exercises?
So right now this doesn't seem to be an issue because it looks like the Trackler gem is handling UUID information, which is taken directly from the config.json. Here's an example https://github.com/exercism/exercism.io/blob/master/api/v1/routes/uuids.rb
However, I suspect that this may change in the future once Nextercism is reading UUIDs from a DB; making the repair option a bit tricky.
@kytrinyx please let me know if I'm off with how things currently work. In the mean time, I will keep this PR pinned and start working on creating PRs in the track repos to fix invalid UUIDs.
Thanks again for the feedback and review.
Is there an impact to the server structure of Exercism if we swap out UUIDs for exercises?
Not on v1. We will need to do a full database refresh on v2, but that's already planned / something we need to do anyway.
I'm wondering if the doctor command is something worth having.
My gut feeling is that it's better as a one-off command for our own use in the period while we're getting everything fixed than a long-term addition.
Closing this PR. I will keep my branch up to date in case we need to fix UUIDs later on.
An initial attempt to adding a diagnostic command for validating and repairing exercise UUIDs within a track. See sample output below.
This is something I put together, as a quick one off, to fix tracks with invalid UUIDs. I'm wondering if the doctor command is something worth having. The command as it stands is a bit rough, in that it reads the raw JSON file, replaces some bits, and spits it back out. Basically, side stepping the whole JSON ordering, munging for now to fix UUIDs.
I would love your thoughts, feedback, and I always welcome the review 🙇