Skip to content

0.4.2

Latest
Latest

Choose a tag to compare

View all tags
@saberzero1 saberzero1 released this 24 Aug 13:30
· 2 commits to master since this release
Immutable release. Only release title and notes can be modified.
0.4.2
This tag was signed with the committer’s verified signature.
saberzero1 Emile Bangma
SSH Key Fingerprint: 1B7+1uiSgSJ1s1f0kU9Pps/fIL5QjW1i41O6NYe1sIw
Verified
Learn about vigilant mode.
d7e2239
This commit was signed with the committer’s verified signature.
saberzero1 Emile Bangma
SSH Key Fingerprint: 1B7+1uiSgSJ1s1f0kU9Pps/fIL5QjW1i41O6NYe1sIw
Verified
Learn about vigilant mode.

New features

  • ruleConfigs export: The plugin now exports ruleConfigs.recommended and ruleConfigs.recommendedTypeChecked, which are the obsidianmd rule severity presets as plain rule objects. These can be spread into a rules block for users who want to use obsidianmd rules with their own ESLint and typescript-eslint setup, without using the full recommended config.

Documentation

  • New configuration guide covering:
    • Why parserOptions is required and how to set it up
    • What the recommended config includes
    • Using the plugin alongside stricter typescript-eslint configs
    • Using only obsidianmd rules without the recommended config
    • Disabling rules for specific files (including bulk-disable via ruleConfigs)
    • Common errors and how to fix them
    • Community plugin scanner configuration, ignore patterns, and a full scanner-equivalent config example
  • Updated README examples to use projectService with allowDefaultProject (the modern typescript-eslint approach), replacing the older parser + project pattern. This fixes the common "requires type information" error when linting eslint.config.mts.
  • Removed legacy .eslintrc documentation — the plugin requires ESLint ≥9.19.0, so legacy config examples were misleading.

Full Changelog: 0.4.1...0.4.2

Assets 3
Loading