1.2.0
Changes
Added a commentPattern option to override the overall comment pattern that matches both term and ticket. When used, term and pattern options are ignored. Expects a regex string.
For example, let's say your IDE or tooling expects a different comment pattern such as TODO: [PROJ-123], you would configure this rule like:
{
"rules": {
"todo-plz/ticket-ref": ["error", { "commentPattern": "TODO:\\s\\[(PROJ-[0-9]+[,\\s]*)+\\]" }]
}
}Thank you @utluiz for the contribution 🎉