Deprecate exercises binary, octal, hexadecimal, and accumulate #138
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
isaacvando
approved these changes
Oct 9, 2024
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.
As @kukimik mentioned in #137 , we have implemented four exercises that were actually deprecated:
binary,octal,hexadecimal(all replaced byall-your-base), andaccumulate(replaced bylist-ops).When an exercise is deprecated, there is a
.deprecatedfile in its.problem-specificationsfolder, for example.problem-specifications/exercises/hexadecimal/.deprecated. I didn't know that.An exercise should never be deleted, instead it must be deprecated by setting its
statuskey to"deprecated"inconfig.json(this is what this PR does), and possibly setting other fields to[]too (see the docs for more details).