📝 Disallow sample code snippets from the Obsidian plugin template.
💼 This rule is enabled in the following configs: ✅ recommended, 🇬🇧 recommendedWithLocalesEn.
🔧 This rule is automatically fixable by the --fix CLI option.
The two example calls from the sample plugin's onload(), which only log to the console or show a
notice on every click:
this.registerInterval(window.setInterval(() => console.log("setInterval"), 5 * 60 * 1000));
this.registerDomEvent(document, "click", (evt: MouseEvent) => {
console.log("click", evt);
});
// The click handler in newer versions of the sample plugin
this.registerDomEvent(activeDocument, "click", (_evt: MouseEvent) => {
new Notice("Click");
});The interval is reported with any delay, such as this.settings.minutes * 60 * 1000. The click
handler, on document or activeDocument, is reported only when its body is that one
console.log("click", …) or new Notice("Click") statement, whatever its parameter is called. The
log may print other values, such as evt.target, but not compute them with a call.
Not reported, because the code is the plugin's own: a click handler with statements of its own,
before or after the log or notice (console.log("click", evt); this.handleClick(evt);), a notice
with other text, an interval callback other than the arrow () => console.log("setInterval")
(a block body, as in () => { console.log("setInterval"); }, included), a log through another log() such as
this.logger.log("click", evt), and other registerInterval() and registerDomEvent() calls.
The fix deletes the statement. When the call is not a statement of its own, such as
const id = this.registerInterval(…), a return or the body of an if without braces, it is
reported without a fix: deleting it would break the code that uses its value or change what the if
controls. It is also reported without a fix when the delay or the listener options call something,
as in window.setInterval(() => console.log("setInterval"), this.getDelay()), since deleting the
call would skip that call too.