chore: remove unused setting

This commit is contained in:
Aleix Soler 2025-07-21 18:55:19 +02:00
parent dfc8ce9ea4
commit ac5c062de6
9 changed files with 3 additions and 56 deletions

View file

@ -92,17 +92,6 @@ export const UISettings: React.FC<Props> = ({ settings, onChange }) => {
/>
</SettingItem>
<SettingItem
name="Exclude unassigned notes from status pane"
description="Excludes unassigned notes from status pane for better performance. Recommended for large vaults."
>
<input
type="checkbox"
checked={settings.excludeUnknownStatus || false}
onChange={handleChange("excludeUnknownStatus")}
/>
</SettingItem>
<h4>Unknown Status Customization</h4>
<SettingItem

View file

@ -20,7 +20,6 @@ export const DEFAULT_PLUGIN_SETTINGS: PluginSettings = {
useMultipleStatuses: true,
tagPrefix: "obsidian-note-status",
strictStatuses: false, // Default to show all statuses from frontmatter
excludeUnknownStatus: true, // Default to exclude unknown status files for better performance
quickStatusCommands: ["active", "completed"], // Add default quick commands
// Unknown status customization
unknownStatusIcon: "❓",

View file

@ -166,8 +166,7 @@ export class GroupedDashboardView extends ItemView {
key === "useCustomStatusesOnly" ||
key === "customStatuses" ||
key === "useMultipleStatuses" ||
key === "strictStatuses" ||
key === "excludeUnknownStatus"
key === "strictStatuses"
) {
onDataChange();
}

View file

@ -151,8 +151,7 @@ export class GroupedStatusView extends ItemView {
key === "useCustomStatusesOnly" ||
key === "customStatuses" ||
key === "useMultipleStatuses" ||
key === "strictStatuses" ||
key === "excludeUnknownStatus"
key === "strictStatuses"
) {
onDataChange();
}

View file

@ -334,8 +334,7 @@ export class StatusDashboardView extends ItemView {
key === "useCustomStatusesOnly" ||
key === "customStatuses" ||
key === "useMultipleStatuses" ||
key === "strictStatuses" ||
key === "excludeUnknownStatus"
key === "strictStatuses"
) {
handleVaultChange();
handleFileChange();

View file

@ -23,7 +23,6 @@ export type PluginSettings = {
useMultipleStatuses: boolean; // Whether to allow multiple statuses per note
tagPrefix: string; // Prefix for the status tag (default: 'status')
strictStatuses: boolean; // Whether to only show known statuses
excludeUnknownStatus: boolean; // Whether to exclude files with unknown status from the status pane
quickStatusCommands: string[];
// Unknown status customization
unknownStatusIcon: string; // Custom icon for unknown status

View file

@ -107,17 +107,6 @@ Icon Position: [Before name | After name]
After name: Shows status after filename (default)
```
#### Status Pane Options
```
☐ Default to compact view
Starts status pane in dense layout mode
✅ Exclude unassigned notes from status pane
Skips files with "unknown" status
CRITICAL for performance with large vaults (>5000 notes)
```
### Status Behavior
#### Multiple Status Support
@ -303,14 +292,6 @@ Ctrl+Shift+S → Change status of current note
### Performance Tuning
#### Large Vault Settings (5000+ notes)
```
✅ Exclude unassigned notes from status pane
✅ Hide unknown status in file explorer
Items per page: 50 (reduce from default 100)
```
#### Memory Optimization
```

View file

@ -4,14 +4,6 @@ Optimize Note Status for large vaults (tested up to 40k notes).
## Quick Wins
### Essential Settings for 5k+ Notes
```
✅ Exclude unassigned notes from status pane
✅ Hide unknown status in file explorer
Pagination: 50-100 items per page
```
### Disable Heavy Features
```
@ -24,7 +16,6 @@ Pagination: 50-100 items per page
```json
{
"showStatusIconsInExplorer": false,
"excludeUnknownStatus": true,
"hideUnknownStatusInExplorer": true,
"enabledTemplates": ["minimal"]
}

View file

@ -82,15 +82,6 @@ Enable a template for instant statuses:
- Select multiple files for batch updates - ![Status Pane Screenshot](images/batch-updates.png)
![File Explorer Screenshot](images/file-explorer.png)
## Performance Setup (Large Vaults)
If you have 1000+ notes, set the settings:
```
✅ Exclude unassigned notes from status pane
✅ Hide unknown status in file explorer
```
## Frontmatter Format
The plugin stores statuses in YAML frontmatter: