A language track's config.json file provides a way to pass data between the track's git repo and the V3 website's ActiveRecord data model. configlet
is a tool for validation and sanitization of the shared config data as it is transferred between the decentralized track repos and the centralized data models.
configlet
is integrated (to varying degrees) into the CI / build process of the language track repos. It is also downloaded and used locally by track maintainers to assist in understanding, validating, and formatting the track config.json
files. As part of exercism V3, we will be evolving the specifications (of config.json
). This provides a good opportunity to analyze the open issues with configlet and evaluate the best path forward.
Based on the analysis below, I would like to consider replacing configlet
with an API (either built into the v3-website or as a standalone service used by the v3-website). As-neede