Currently the todochecker can only detect a todo if it is written all uppercase (like # TODO: Lorem ipsum ...). In some cases the todo may not br written in all uppercase but a different casing like all lowercase (which is sometimes common for annotations: /** @todo: Lorem ipsum ... */ or camelcase: # ToDo: Lorem ipsum .... These other casings are currently not detected by todocheck. This me
Simple starter webpack project template with support for SASS, Babel ES7, browser syncing, source code listing and more. Easy project boilerplate setup having multiple features and developer friendly tools.
// makeExample replaces all ${linter} placeholders to a bound linter name.
The code below does not use ${linter} anywhere.
I could remove this, but would also like to avoid doing several unrelated things on the same PR, so keeping it as an issue to avoid forgetting about it.
The whole idea of writing code to check another code is intriguing at the same time cognitively demanding. Building Linters for Ruby, the project provides feedback about errors or warning in code little by little. The project was built completely with Ruby following all possible best practices. Rubocop was used as a code-linter alongside Gitflow to ensure I maintain good coding standards.
Currently the todochecker can only detect a todo if it is written all uppercase (like
# TODO: Lorem ipsum ...). In some cases the todo may not br written in all uppercase but a different casing like all lowercase (which is sometimes common for annotations:/** @todo: Lorem ipsum ... */or camelcase:# ToDo: Lorem ipsum .... These other casings are currently not detected by todocheck. This me