Add back deleted, deprecated exercises#503
Conversation
|
@kytrinyx Do they have to be actually working exercises? As of now, they don't follow the newly introduced project format. That is at the least inconsistent, but possibly also erroneous. Should people that once worked on these exercises be allowed to work on them again? |
Yes in terms of they need the files etc. No in terms of them needing all the same level of config (e.g. topics, difficulty, etc). I'm 👍 to this @kytrinyx, but let's check it in a sample ETL run to be sure. |
Hm. Yeah, they do need to actually work. I'll read through the track documentation and get this to conform. |
e7dca94 to
b36dbee
Compare
|
@ErikSchierboom Would you take a look to see if this is properly following the project structure? |
|
The build is failing because I've not yet converted the test suite. I'll give that a go next. |
|
Thanks for doing this! I'll take a look tomorrow. By the way, you can verify the build by running build.sh or build.cmd (also works for the F# track). |
Ah! That's helpful thanks! |
|
Oh, and you can test build single exercises using --exercise= |
|
That is --exercise=slug |
|
Sweet, thanks! |
When migrating the data from v1 to v2, we will lose all the solutions submitted to deprecated exercises, unless they are configured. This adds the deprecated binary, trinary, octal, and hexadecimal exercises back, leaving them deprecated so that they don't actively show up as part of the track.
b36dbee to
667080e
Compare
|
Thanks a lot! |
When migrating the data from v1 to v2, we will lose all the solutions submitted to
deprecated exercises, unless they exist in the track configuration.
This adds the deprecated binary, trinary, octal, and hexadecimal exercises back,
leaving them deprecated so that they don't actively show up as part of the track.
We can delete them from the track again after we launch v2, if we want to.