-
-
Notifications
You must be signed in to change notification settings - Fork 624
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add scale-generator exercise #754
add scale-generator exercise #754
Conversation
Sweet. We'll review this. You did great with the config.
|
Yup, I used a uuidgen. And the topics are covered by the exercise; I can add more if you think there are other relevant topics! How do we determine the unlock exercise? Is it intended to be the same for all tracks or does it depend on the track? The Python version uses |
Good question! Each track has its own core. You can see it here for JavaScript, in bold. Each side exercise is unlocked by a core exercise. Since tracks are not the same across languages, neither are the unlocks. Usually I do the following:
If we look at the Python track, we can see that |
Thanks for the guidance @SleeplessByte ! Looking at pangram, I agree it's a good candidate for unlocking this one, since it looks like there are similar matching and arrays elements. I'll push up an update for |
f234176
to
f30d75c
Compare
Let's do this! |
@seeksort if you have 5 more minutes, would you be so kind and see if you can help us out by responding to this issue? Awesome work on this. Let's see how this propagates :) |
Yay! And it deployed so quickly! Sure, I'll check it out. Thanks again for your help! |
Adding scale-generator exercise. Closes #751.
One thing I'm not sure about is updating
config.json
. I just based it on the same entry in other tracks, not sure if there's other stuff I should consider.