Change unlocking order step 1 #827
Merged
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.
This:
'unlocked_by: null
tohello-world
)unlocked_by: null
move up one or two levels ( unlocked either by TwoFer or by Hamming).In #518 the request was to restrict the number of
unlocked_by: null
to 4 or 5 exercises.Am I right that
unlocked_by: hello-world
has the same effect in the track? I used that, to make it more explicit.This PR is an intermediate step in the Ruby Overhaul™.
As a temporary step, all the other exercises that used_to be
unlocked_by: null
are now moved up 1 or 2 levels, so either by TwoFer for the lowest difficulties, or Hamming, for most others, and some with the highest difficulties quite arbitrary by later core exercises.I also lowered the difficulty for a few exercises, but they should still be in the same 'easy' category.