Remove obsolete problems key #171
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The `problems` key has been obsoleted as per [this issue](exercism/DEPRECATED.x-api#137). This has already been succesfully implemented by the [C#](https://github.com/exercism/xcsharp#130), [F#](https://github.com/exercism/xfsharp#224) and [Haskell](exercism/haskell#399) tracks, so API-wise this is a safe action. Removing the `problems` key also makes it very impossible for people to only add a new exercise in the old, obsolete `problems` key.
ErikSchierboom
force-pushed
the
remove-obsolete-problems-key
branch
from
502ba5a
to
936895a
Compare
|
The build script also had to be modified, as it looked for the list of exercise names in the old |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
problemskey has been obsoleted as per this issue. This has already been succesfully implemented by the C#, F# and Haskell tracks, so API-wise this is a safe action.Removing the
problemskey also makes it very impossible for people to only add a new exercise in the old, obsoleteproblemskey.