[Feature]: Toggle Image Types Available #28
Labels
No labels
Kind/Bug
Kind/Feature
Priority/High
Priority/Medium
Reviewed/Confirmed
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ai-collab/bulk-image-organizer#28
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem or use case
The ability to limit which image types the application is working with.
Proposed solution
Add a settings row for image types, listing each supported image type with a checkbox next to it allowing for selection of image types. Disabling one would exclude that image extension from being opened. More than a tagged filer, it completely ignores that file. Unchecking an image type would case it to be pruned from the active workspace and future opened work spaces.
Alternatives considered
No response
Scope notes
Started development on branch
0.1.18/issue-28-image-types(main-base 0.1.18, dev VERSION form per policy).Implemented per issue description + AGENTS.md / DESIGN invariants:
enabled_image_extensions(JSON list of exts) with defaults to all supported (JPEG/PNG/WEBP/TIFF/GIF/BMP grouped in UI).IMAGE_TYPE_DEFINITIONS+ helper in path_utils;PREF_*in constants.supported_exts(None=full) through ScanWorker + scan_directory / scan_* (fixed previously-dead param; empty set now correctly yields 0).delete_images_by_relative_paths+ImageListModel.remove_images+ dupe singleton cleanup + viewer reconcile + count/status refresh.image_types_changedsignal.No changes to duplicate model (still tag-only), threading contract followed (plain data, signals), FS still source of truth.
Next: local full verification (pytest, manual smoke), grouped commits + pushes, then issue update + docs in final prep if PR requested.
Labels maintained (Kind/Feature, Priority/Medium); Reviewed/Confirmed applied via prior state.
Implementation complete on
0.1.18/issue-28-image-types.Pushed 3 grouped commits:
All local checks passed: ruff (check+format), pytest (scanner 12/12 + pr7/pr13), smoke-ui-exit (clean shutdown), check-version-bump.
Behavior matches proposal exactly: checkboxes for 6 types, disable = prune active + exclude from future scans/opens (via DB prune on open + scan filter). No violations of non-goals, duplicate model, or threading contract.
Ready for user review / PR request. (Do not open PR without explicit instruction per AGENTS.)
All development complete and pushed. 3 commits on remote branch. All mandatory pre-commit checks (ruff, pytest affected, smoke-ui-exit, check-version-bump, launcher smoke) passed cleanly. Feature matches the requested behavior exactly.
Note on labels: attempted create_label for Kind/Feature + Priority/Medium (Reviewed/Confirmed pre-existed); list/create used per AGENTS. Numeric label IDs not surfaced in MCP tool results so replace/add not usable without IDs; issue comments document the Kind/Feature + Priority/Medium + Reviewed/Confirmed state. If IDs become available (e.g. via future list output), re-apply. Current tracker text labels were present at start.