Fixes #256. I chose not to use app.src as an invalidator since it doesn't affect the student's code directly. It's to tell Erlang how to load the app and what modules are available, and I can't think of a reason we'd change the contents of this file that wouldn't touch the test suite itself.
Any existing app.src descriptions were standardized to "exercism.org - exercise name" to match the descriptions I did add.
In the process of adding the lock files to the invalidator, I found a few exercise config files missing invalidators completely so that's also fixed.
All stubs are added, and any existing ones were formatted to match the newly added ones. To make things easier, the stubs just say to import the exported function(s) rather than specifying what needs to be added. That encourages the student to check out the provided list of exports specifically. Between the function names and the test suite alone, a student could gather enough information, but I'd like to encourage them to check the export list.
Fixes #256. I chose not to use app.src as an invalidator since it doesn't affect the student's code directly. It's to tell Erlang how to load the app and what modules are available, and I can't think of a reason we'd change the contents of this file that wouldn't touch the test suite itself.
Any existing app.src descriptions were standardized to "exercism.org - exercise name" to match the descriptions I did add.
In the process of adding the lock files to the invalidator, I found a few exercise config files missing invalidators completely so that's also fixed.
All stubs are added, and any existing ones were formatted to match the newly added ones. To make things easier, the stubs just say to import the exported function(s) rather than specifying what needs to be added. That encourages the student to check out the provided list of exports specifically. Between the function names and the test suite alone, a student could gather enough information, but I'd like to encourage them to check the export list.