lint: Check that UUIDs are valid #168
Conversation
|
Note this list of exercises and their associated tracks that currently have invalid UUIDs: invalid elm isogram: 5f540090-061e-2f80-40a8-d9782700ed2efdf8965: invalid UUID length: 43 |
all tests that involve lint are hereby updated to do one of the two: 1. have valid UUIDs 2. keep their invalid UUIDs, and expect that an error for them is shown. Closes exercism/configlet#99
|
We need to figure out what would have to happen in the database to change UUIDs to be valid, where they are not. Currently, fixing invalid UUIDs breaks the site pretty badly. |
|
It looks like this PR will have to wait until those issues are solved. I sympathise with this plight - it means that it would currently be unwise to release a configlet with this change - affected tracks' The motivation for having this PR is to prevent any additional invalid UUIDs from being added. Since we see that configlet currently can't be the place where this is enforced, I will do so in individual tracks' CI of tracks I maintain. Thus achieving the original motivation without causing trouble for all tracks and the website. When the above issues are solved and configlet is able to enforce this, then it will be a good time to revisit this PR and remove the checks from individual tracks. |
Want to prevent any invalid UUIDs from being entered. Want to put this in configlet lint, but can't: exercism/configlet#99 exercism/configlet#168 So it will go in individual tracks' .travis.yml for now. It appears that the site will accept pretty much arbitrary strings as UUIDs for now, but we want to make less work for ourselves when valid UUIDs are required.
Want to prevent any invalid UUIDs from being entered. Want to put this in configlet lint, but can't: exercism/configlet#99 exercism/configlet#168 So it will go in individual tracks' .travis.yml for now. It appears that the site will accept pretty much arbitrary strings as UUIDs for now, but we want to make less work for ourselves when valid UUIDs are required.
Want to prevent any invalid UUIDs from being entered. Want to put this in configlet lint, but can't: exercism/configlet#99 exercism/configlet#168 So it will go in individual tracks' .travis.yml for now. It appears that the site will accept pretty much arbitrary strings as UUIDs for now, but we want to make less work for ourselves when valid UUIDs are required.
Want to prevent any invalid UUIDs from being entered. Want to put this in configlet lint, but can't: exercism/configlet#99 exercism/configlet#168 So it will go in individual tracks' .travis.yml for now. It appears that the site will accept pretty much arbitrary strings as UUIDs for now, but we want to make less work for ourselves when valid UUIDs are required.
Want to prevent any invalid UUIDs from being entered. Want to put this in configlet lint, but can't: exercism/configlet#99 exercism/configlet#168 So it will go in individual tracks' .travis.yml for now. It appears that the site will accept pretty much arbitrary strings as UUIDs for now, but we want to make less work for ourselves when valid UUIDs are required.
Want to prevent any invalid UUIDs from being entered. Want to put this in configlet lint, but can't: exercism/configlet#99 exercism/configlet#168 So it will go in individual tracks' .travis.yml for now. It appears that the site will accept pretty much arbitrary strings as UUIDs for now, but we want to make less work for ourselves when valid UUIDs are required.
* travis: reject invalid UUIDs Want to prevent any invalid UUIDs from being entered. Want to put this in configlet lint, but can't: exercism/configlet#99 exercism/configlet#168 So it will go in individual tracks' .travis.yml for now. It appears that the site will accept pretty much arbitrary strings as UUIDs for now, but we want to make less work for ourselves when valid UUIDs are required.
all tests that involve lint are hereby updated to do one of the two:
Closes exercism/configlet#99