Right now the readme insert is the docs/EXERCISE_README_INSERT.md.
If none of the track's exercises override the readme template by sticking a template in the .meta directory, then the template is not necessary.
However, if an exercise does override the README, then we lose the ability to use template variables in the insert. We need the template variables to correctly generate the command for running the tests.
E.g.: in JavaScript
jasmine {{ .Spec.Slug }}.spec.js
In Ruby:
ruby {{ .Spec.SnakeCaseName}}_test.rb
Or, if a file is named with mixed case, we can use {{ .Spec.MixedCaseName }}.
So, in order to support readme overrides, I'd like to add support for a file config/exercise_readme_insert.tmpl.go which would be used in preference in place of docs/EXERCISE_README_INSERT.md or ./HINTS.md, both of which would be deprecated.
Right now the readme insert is the
docs/EXERCISE_README_INSERT.md
.If none of the track's exercises override the readme template by sticking a template in the
.meta
directory, then the template is not necessary.However, if an exercise does override the README, then we lose the ability to use template variables in the insert. We need the template variables to correctly generate the command for running the tests.
E.g.: in JavaScript
In Ruby:
Or, if a file is named with mixed case, we can use
{{ .Spec.MixedCaseName }}
.So, in order to support readme overrides, I'd like to add support for a file
config/exercise_readme_insert.tmpl.go
which would be used in preference in place ofdocs/EXERCISE_README_INSERT.md
or./HINTS.md
, both of which would be deprecated.