Skip to content

DO NOT MERGE: we broke it in all three ways#1075

Closed
petertseng wants to merge 4 commits intoexercism:masterfrom
petertseng:ci-new-schema-strict-breakit
Closed

DO NOT MERGE: we broke it in all three ways#1075
petertseng wants to merge 4 commits intoexercism:masterfrom
petertseng:ci-new-schema-strict-breakit

Conversation

@petertseng
Copy link
Copy Markdown
Member

@petertseng petertseng commented Jan 5, 2018

test #1074

@petertseng
Copy link
Copy Markdown
Member Author

As expected:

Exercises using old schema, but invalid:  alphametics
Exercises using new schema, but invalid:  acronym
Exercises using new schema, but forgot to remove USE_OLD_SCHEMA file:  anagram

@@ -1,4 +1,5 @@
{
this is completely invalid json, under the new schema
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

incorrect comment. this should say old schema.

@petertseng petertseng reopened this Jan 5, 2018
@petertseng
Copy link
Copy Markdown
Member Author

Exercises using old schema, but invalid: alphametics
Exercises using new schema, but invalid: acronym
Exercises using new schema, but forgot to remove USE_OLD_SCHEMA file: anagram

@petertseng petertseng closed this Jan 5, 2018
@petertseng petertseng reopened this Jan 5, 2018
@petertseng petertseng closed this Jan 5, 2018
@petertseng petertseng reopened this Jan 15, 2018
@petertseng petertseng closed this Jan 15, 2018
@petertseng petertseng reopened this Jan 24, 2018
@petertseng petertseng closed this Jan 24, 2018
Derived from the list of invalid exercises listed in:
#998 (comment)
This schema was proposed and accepted in
#996
@petertseng petertseng reopened this Feb 10, 2018
@petertseng petertseng closed this Feb 10, 2018
If it is present, use the old schema, else use the new schema.

This plan is proposed in:
#998

Its merits are that it allows us to:

* Track progress by simply counting number of USE_OLD_SCHEMA file.
* Verify, as each PR is made, that each JSON file intending to use new
  schema does in fact validate.
  * Otherwise we have to manually run a schema check at periodic
    intervals.
* Keep compatibility with old schema, to support moving over one file at
  a time instead of all at once.

Note that old-schema.json is the same canonical-schema.json as is
currently on master.

The intention is that when all exercises use the new schema, **this
commit can/should be reverted** and then all exercises will in fact use
the new schema, which will replace the old completely.
@petertseng petertseng reopened this Feb 10, 2018
@petertseng petertseng closed this Feb 10, 2018
@petertseng petertseng deleted the ci-new-schema-strict-breakit branch February 10, 2018 12:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant