exercism / legacy-docs

Other
84 stars 55 forks source link

Is unlocked-by always required for non-core exercises? #113

Closed tejasbubane closed 6 years ago

tejasbubane commented 6 years ago

Came across this while changing the config to configlet 3.8.0 in https://github.com/exercism/javascript/issues/527

The config spec says:

All optional exercises should be unlocked by one of the core exercises.

This made me think that all optionals should have this property - later found out that tracks have kept it null at many places. eg. ruby config. Also the latest version of configlet allows having null values.

Should unlocked-by be a required property? If not can we mention so in the spec?

tleen commented 6 years ago

The docs may need to be updated. core:false and unlocked_by: null indicate a bonus exercise. One that is available at the start of the track in case users want to try another exercise besides core right away. I believe this is still the case.

kytrinyx commented 6 years ago

I believe this is still the case.

Yepp, that's still the case.