Bug: Linter Runs Custom Commands even When All Custom Commands Are Blank about obsidian-linter HOT 5 CLOSED

I have gone ahead and merged what I believe should prevent the scenario you saw with the invalid running of custom commands. It should be in master now and go out in the next release. Please let us know if either has a problem.

from obsidian-linter.

Hey @sisi-sh , thanks for mentioning this. It looks like you have a blank custom command which is causing this behavior.

When custom commands exists, there is a need to have a file open in order to run the custom commands. Thus on active file change, which fires after the the active file has changed, I have to open the last opened file in the sidebar to run custom commands.

It seems this is not the first time that users have accidentally created or left a blank custom command in their config as their only custom command which causes problems, so I am guessing I need to have a boolean setup to determine if the custom commands present include any valid custom commands and use that to determine what to do with custom commands since the length is not viable.

from obsidian-linter.

Oh awesome that did fix it. Thanks!

from obsidian-linter.

That's good. I will see about handling all blank custom commands.

But using custom commands will create that experience with lint on file change since the previous file has to be the active file in order for the custom commands to run properly.

from obsidian-linter.

I believe I have a fix for blank custom commands running in the sidebar. However I would like to make it clear that custom commands running in the sidebar is expected when custom commands are present and you have lint on file change enabled.

from obsidian-linter.