-
-
Notifications
You must be signed in to change notification settings - Fork 544
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
canonical-data.json: Compliance with JSON Schema #625
Comments
The final goal here is that we will be able to run every canonical-data.json through a schema check, right? Then can I propose we do not wait until all canonical-data.json are compliant before starting to do that? Let's start check them all ASAP, and allow those listed in a file named allowed-schema-failures (or something) to fail. Because we wouldn't want a file that was compliant to fall out of compliance while this project is underway. The goal of course will be to drive the number of lines in the file down to zero. |
If anyone wants to port and exercise to the new schema, I is a good idea to say here, so that we don't make useless duplicated work. |
Working on Hamming |
|
I'll tackle |
|
I've got |
|
|
|
generator: slugs everywhere [closes #624]
Relevant PRs: - exercism/problem-specifications#625 - exercism/problem-specifications#844 - exercism/problem-specifications#845 - exercism/problem-specifications#875 - exercism/problem-specifications#953 - exercism/problem-specifications#1129 - exercism/problem-specifications#1389 Basically adds every test case from the current canonical-data.json without deleting the old ones.
Relevant PRs: 1) Test cases: - exercism/problem-specifications#625 - exercism/problem-specifications#844 - exercism/problem-specifications#845 - exercism/problem-specifications#875 - exercism/problem-specifications#953 - exercism/problem-specifications#1129 - exercism/problem-specifications#1389 2) README: - exercism/problem-specifications#1360 Basically adds every test case from the current canonical-data.json without deleting the old ones.
Now that #602 was merged, it would be great to have all the
canonical-data.json
files compliant with the JSON Schema, so that we could automatically check them for errors in the future.At the moment, we have 74
canonical-data.json
files, but only 3 are compliant.When porting the files, I guess it would be nice to follow a few guidelines to make reviewing easier:
exercise-name: Make canonical-data.json compliant
, containing the minimal changes to make the test suite compliant.exercise-name: Fix canonical-data.json formatting
, with the changes needed to make it readable again.exercise-name: Make exercise schema-compliant
Related to #625
.version
should start at 1.0.0 and follow theexercise
property.Unless there is already a standard in place that I don't know, I suggest formatting with 2-spaces indentation in the second commit, for consistency, which is already the default when running
jq '.' canonical-data.json
.Of course, most of the exercises will demand additional changes to a standard formatting, to make them more compact and readable.
Edit: Just to be clear, this issue is not about style in designing the test suite. Changes that go beyond fixing the test suite to be compliant and fix it to be consistently formatted after that should be avoided here!
canonical-data.json
complianceThe text was updated successfully, but these errors were encountered: