You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 22, 2022. It is now read-only.
Based on exercism/javascript#433, I feel that configlet lint should error on any exercise that has "core": true but also is "deprecated": true. Right now, with this configuration it blocks someone from moving on to the next exercise in the track.
The text was updated successfully, but these errors were encountered:
@amscotti thanks for opening up this issue. This seems like a bug on the Exercism backend side as well if it is indeed showing exercises which are set to be unlocked by deprecated exercises. @iHiD ☝️
None the less, I agree that we should have a check for this case. If anything two checks. One that deprecated exercises are not core, two that an exercise is not set to be unlocked by a deprecated exercise.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Based on exercism/javascript#433, I feel that
configlet lint
should error on any exercise that has"core": true
but also is"deprecated": true
. Right now, with this configuration it blocks someone from moving on to the next exercise in the track.The text was updated successfully, but these errors were encountered: