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 was archived by the owner on May 30, 2023. It is now read-only.
This issue is part of the migration to v3. You can read full details about the various changes here.
There are several new features in Exercism v3 for tracks to build. To selectively enable these features on the Exercism v3 website, each track must keep track of the status of the following features:
The status of these features is specified in the top-level "status" field in the track's config.json, as specified in the spec.
Goal
The "status" field in the config.json file should be updated to indicate the status of the features for this track. The list of features is defined in the spec.
This issue is part of the migration to v3. You can read full details about the various changes here.
There are several new features in Exercism v3 for tracks to build. To selectively enable these features on the Exercism v3 website, each track must keep track of the status of the following features:
The status of these features is specified in the top-level
"status"field in the track'sconfig.json, as specified in the spec.Goal
The
"status"field in theconfig.jsonfile should be updated to indicate the status of the features for this track. The list of features is defined in the spec.Example
{ "status": { "concept_exercises": true, "test_runner": true, "representer": false, "analyzer": false } }Tracking
exercism/v3-launch#12