obsidian-dev-skills 1.1.3 → 1.1.4

package/obsidian-dev/references/code-patterns.md

@@ -130,119 +130,16 @@ class MySettingTab extends PluginSettingTab {
 this.addSettingTab(new MySettingTab(this.app, this));
 ```
 
-## Settings with Groups (Conditional / Backward Compatible)
+## Settings with Groups
 
 **Source**: Based on `.ref/obsidian-api/obsidian.d.ts` (API is authoritative) - `SettingGroup` requires API 1.11.0+
 
-**Use this when**: You want to use `SettingGroup` for users on Obsidian 1.11.0+ while still supporting older versions. This provides conditional settings groups that automatically use the modern API when available, with a fallback for older versions.
+**Use this when**: You want to visually group related settings together.
 
-**Note**: Use the backward compatibility approach below to support both users on Obsidian 1.11.0+ and users on older versions. Alternatively, you can choose to:
-- Continue using the compatibility utility (supports all versions)
-- Force `minAppVersion: "1.11.0"` in `manifest.json` and use `SettingGroup` directly (simpler, but excludes older versions)
-
-### Step 1: Create the Compatibility Utility
-
-Create `src/utils/settings-compat.ts` (or wherever you keep utilities):
-
-```ts
-/**
- * Compatibility utilities for settings
- * Provides backward compatibility for SettingGroup (requires API 1.11.0+)
- */
-import { Setting, requireApiVersion } from 'obsidian';
-
-/**
- * Type definition for SettingGroup constructor
- * Note: SettingGroup may exist at runtime in 1.11.0+ but may not be in TypeScript definitions
- * 
- * IMPORTANT: This type signature is inferred from usage patterns. When .ref/obsidian-api/obsidian.d.ts
- * is available, verify the actual signature there. The signature shown here matches the expected
- * behavior based on Obsidian's API design patterns.
- */
-type SettingGroupConstructor = new (containerEl: HTMLElement) => {
-  setHeading(heading: string): {
-    addSetting(cb: (setting: Setting) => void): void;
-  };
-};
-
-/**
- * Interface that works with both SettingGroup and fallback container
- */
-export interface SettingsContainer {
-  addSetting(cb: (setting: Setting) => void): void;
-}
-
-/**
- * Creates a settings container that uses SettingGroup if available (API 1.11.0+),
- * otherwise falls back to creating a heading and using the container directly.
- * 
- * Uses requireApiVersion('1.11.0') to check if SettingGroup is available.
- * This is the official Obsidian API method for version checking.
- * 
- * IMPORTANT: We use dynamic require() instead of direct import because SettingGroup
- * may not be in TypeScript type definitions even if it exists at runtime in 1.11.0+.
- * This avoids compile-time TypeScript errors while still working at runtime.
- * 
- * @param containerEl - The container element for settings
- * @param heading - The heading text for the settings group (optional)
- * @param manifestId - The plugin's manifest ID for CSS scoping (required for fallback mode)
- * @returns A container that can be used to add settings
- */
-export function createSettingsGroup(
-  containerEl: HTMLElement,
-  heading?: string,
-  manifestId?: string
-): SettingsContainer {
-  // Check if SettingGroup is available (API 1.11.0+)
-  // requireApiVersion is the official Obsidian API method for version checking
-  if (requireApiVersion('1.11.0')) {
-    // Use dynamic require() to access SettingGroup at runtime
-    // This avoids TypeScript errors when SettingGroup isn't in type definitions
-    // eslint-disable-next-line @typescript-eslint/no-require-imports
-    const obsidian = require('obsidian');
-    const SettingGroup = obsidian.SettingGroup as SettingGroupConstructor;
-    
-    // Use SettingGroup - it's guaranteed to exist if requireApiVersion returns true
-    const group = heading 
-      ? new SettingGroup(containerEl).setHeading(heading)
-      : new SettingGroup(containerEl);
-    return {
-      addSetting(cb: (setting: Setting) => void) {
-        group.addSetting(cb);
-      }
-    };
-  } else {
-    // Fallback path (either API < 1.11.0 or SettingGroup not found)
-    // Add scoping class to containerEl to scope CSS to only this plugin's settings
-    if (manifestId) {
-      containerEl.addClass(`${manifestId}-settings-compat`);
-    }
-    
-    // Fallback: Create a heading manually and use container directly
-    if (heading) {
-      const headingEl = containerEl.createDiv('setting-group-heading');
-      headingEl.createEl('h3', { text: heading });
-    }
-        
-    return {
-      addSetting(cb: (setting: Setting) => void) {
-        const setting = new Setting(containerEl);
-        cb(setting);
-      }
-    };
-  }
-}
-```
-
-**Note**: The dynamic `require()` approach is necessary because `SettingGroup` may not be in TypeScript type definitions even if it exists at runtime in Obsidian 1.11.0+. This avoids compile-time TypeScript errors while maintaining runtime compatibility.
-
-### Step 2: Use in Settings Tab
-
-Update your settings tab to use the compatibility utility:
+**Important**: You must set `minAppVersion: "1.11.0"` in your `manifest.json` to use `SettingGroup`.
 
 ```ts
-import { App, PluginSettingTab, Setting } from "obsidian";
-import { createSettingsGroup } from "./utils/settings-compat";
+import { App, PluginSettingTab, Setting, SettingGroup } from "obsidian";
 
 interface MyPluginSettings {
   generalEnabled: boolean;
@@ -271,7 +168,7 @@ class MySettingTab extends PluginSettingTab {
     containerEl.empty();
 
     // General Settings Group
-    const generalGroup = createSettingsGroup(containerEl, "General Settings", "my-plugin");
+    const generalGroup = new SettingGroup(containerEl).setHeading("General Settings");
     
     generalGroup.addSetting((setting) => {
       setting
@@ -304,7 +201,7 @@ class MySettingTab extends PluginSettingTab {
     });
 
     // Advanced Settings Group
-    const advancedGroup = createSettingsGroup(containerEl, "Advanced Settings", "my-plugin");
+    const advancedGroup = new SettingGroup(containerEl).setHeading("Advanced Settings");
     
     advancedGroup.addSetting((setting) => {
       setting
@@ -343,69 +240,9 @@ class MySettingTab extends PluginSettingTab {
 this.addSettingTab(new MySettingTab(this.app, this));
 ```
 
-### Step 3: Add CSS Styling (Required for Older Obsidian Builds)
-
-**Important**: When using the compatibility utility for older Obsidian builds (< 1.11.0), you must add CSS to prevent double divider lines. The fallback creates a heading with class `setting-group-heading`, and without proper CSS, you'll see a double divider (one from the heading's border-bottom and one from the first setting-item's border-top).
-
-**CRITICAL**: The CSS **MUST** be scoped to your plugin's settings container using a manifest-ID-based class to avoid affecting other plugins' settings. Global CSS selectors will impact all settings in Obsidian, not just your plugin's settings.
-
-Add this CSS to your `styles.css` file, replacing `{manifest-id}` with your plugin's manifest ID:
-
-```css
-/* Group settings compatibility styling for older Obsidian builds (< 1.11.0) */
-/* Scoped to only this plugin's settings container to avoid affecting other plugins */
-.{manifest-id}-settings-compat .setting-group-heading h3 {
-    margin: 0 0 0.75rem;
-    padding-bottom: 0.5rem;
-    padding-top: 0.5rem;
-    font-size: 1rem;
-    font-weight: 600;
-    border-bottom: none !important;
-}
-```
-
-**Example**: If your manifest ID is `sample-plugin`, use `.sample-plugin-settings-compat` as the scoping class.
-
-**How it works**:
-- The CSS uses the `:has()` selector to detect if a `.setting-item` immediately follows the heading
-- If settings exist below the heading, no border-bottom is applied (avoiding double divider)
-- If no settings follow, border-bottom is applied for visual separation
-- The scoping class (`{manifest-id}-settings-compat`) ensures CSS only affects headings within this plugin's settings container
-- This only affects older builds (< 1.11.0) where the compatibility fallback is used
-- On Obsidian 1.11.0+, `SettingGroup` handles styling automatically, so this CSS has no effect
-
-**Note**: The `:has()` selector is well-supported in modern Obsidian (Chromium-based). If you need to support very old browsers, see the alternative TypeScript-based approach in the Common Pitfalls section below.
-
-### How It Works
-
-- **On Obsidian 1.11.0+**: Uses `SettingGroup` with proper styling and grouping
-- **On older versions**: Creates a manual heading (`<h3>`) and uses regular `Setting` objects
-- **Same API**: Your code using `addSetting()` works identically in both cases
-
 ### Common Pitfalls
 
-#### Pitfall 1: TypeScript Errors with SettingGroup Import
-
-**Problem**: You may see this TypeScript error:
-```ts
-Module '"obsidian"' has no exported member 'SettingGroup'
-```
-
-**Cause**: `SettingGroup` may exist at runtime in Obsidian 1.11.0+ but may not be in the TypeScript type definitions, causing compile-time errors.
-
-**Solution**: Use dynamic `require()` instead of direct import, as shown in the compatibility utility above. Do not import `SettingGroup` directly:
-
-```ts
-// ❌ WRONG - Causes TypeScript errors
-import { SettingGroup } from 'obsidian';
-
-// ✅ CORRECT - Use dynamic require()
-// eslint-disable-next-line @typescript-eslint/no-require-imports
-const obsidian = require('obsidian');
-const SettingGroup = obsidian.SettingGroup as SettingGroupConstructor;
-```
-
-#### Pitfall 2: Missing Closing Parentheses
+#### Pitfall 1: Missing Closing Parentheses
 
 **Problem**: Arrow functions with method chaining need proper closing parentheses and semicolons.
 
@@ -431,7 +268,7 @@ generalGroup.addSetting((setting) =>
 ); // Closing parenthesis and semicolon required
 ```
 
-#### Pitfall 3: Storing Setting References
+#### Pitfall 2: Storing Setting References
 
 **Problem**: If you need to reference a `Setting` object later (e.g., for visibility toggling), you must use block syntax `{ }` instead of expression syntax.
 
@@ -460,27 +297,6 @@ generalGroup.addSetting((setting) => {
 mySetting.settingEl.style.display = this.plugin.settings.enabled ? "" : "none";
 ```
 
-### Alternative: Force Minimum Version
-
-If you don't need to support versions before 1.11.0, you can skip the compatibility utility:
-
-1. Set `minAppVersion: "1.11.0"` in your `manifest.json`
-2. Use `SettingGroup` directly:
-
-```ts
-import { Setting, SettingGroup } from "obsidian";
-
-// In settings tab:
-const group = new SettingGroup(containerEl).setHeading("My Settings");
-group.addSetting((setting) => {
-  // ... configure setting
-});
-```
-
-**Note**: Even with `minAppVersion: "1.11.0"`, you may still encounter TypeScript errors if `SettingGroup` isn't in the type definitions. In that case, you can still use the compatibility utility approach (it will always use `SettingGroup` when `requireApiVersion('1.11.0')` returns true), or use dynamic `require()` as shown in the compatibility utility.
-
-This approach is simpler but excludes users on older Obsidian versions. The compatibility utility still works and is recommended for maximum flexibility.
-
 ## Modal with Form Input
 
 **Source**: Based on `.ref/obsidian-plugin-docs/docs/guides/modals.md`

package/obsidian-dev/references/commands-settings.md

@@ -16,9 +16,6 @@ Applicability: Plugin
 
 ## Version Considerations
 
-When using newer API features (e.g., `SettingGroup` since API 1.11.0), consider backward compatibility:
-- **For new plugins**: You can set `minAppVersion: "1.11.0"` in `manifest.json` and use the feature directly
-- **For existing plugins**: Use version checking with `requireApiVersion()` to support both newer and older Obsidian versions
-- See [code-patterns.md](code-patterns.md) for backward compatibility patterns, including a complete example for `SettingGroup`
+When using newer API features (e.g., `SettingGroup` since API 1.11.0), you must set `minAppVersion: "1.11.0"` in your `manifest.json`.
 
 

package/obsidian-dev/references/common-tasks.md

@@ -137,7 +137,7 @@ this.addSettingTab(new MySettingTab(this.app, this));
 - `addSearch(cb: (component: SearchComponent) => any)` - Add a search input at the beginning of the group (useful for filtering)
 - `addExtraButton(cb: (component: ExtraButtonComponent) => any)` - Add an extra button to the group
 
-**Backward Compatibility**: To support users on both Obsidian 1.11.0+ and older versions, use a compatibility utility. See [code-patterns.md](code-patterns.md) for the complete implementation with `createSettingsGroup()` utility. Alternatively, you can force `minAppVersion: "1.11.0"` in `manifest.json` if you don't need to support older versions.
+**Important**: You must set `minAppVersion: "1.11.0"` in your `manifest.json` to use these methods.
 
 ## Secret Storage
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "obsidian-dev-skills",
-  "version": "1.1.3",
+  "version": "1.1.4",
   "description": "Agent skills for Obsidian plugin and theme development",
   "keywords": [
     "obsidian",