Exercises with diff > 4: Add stub files#1735
Merged
FridaTveit merged 1 commit intoexercism:masterfrom Sep 25, 2019
Merged
Conversation
FridaTveit
approved these changes
Sep 25, 2019
Contributor
FridaTveit
left a comment
There was a problem hiding this comment.
Looks great, thanks @lemoncurry! 😄
This file contains hidden or 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
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.
Closes #1721.
This PR adds stub files to exercises with difficulty > 4, adds the text agreed on in PR #1723 and removes .keep files.
Deprecated exercises (with difficulty level of 0) are unaffected by this change.
Also, a small number of exercises already provided a starter implementation because of difficult method signatures (binary-search-tree, etl, list-ops) or because the purpose of the exercise is to use refactoring tools (markdown, tree-building).
Some exercises also provided enum or exception classes, nevertheless a stub file was added as a stub for the "main" class of the exercise.
File names reflect the naming choice of the respective test class of the exercise.
I have not changed the integration of the HINT.md files into the README.md. A generic text was sometimes used but often there were specific hints for the respective exercise, so I the README.md is I think still the best place for presenting hints.
Reviewer Resources:
Track Policies