feat: Implement bulk operations for task management #192
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bulk operations for cards have felt like a big benefit, allowing me to tag multiple things at once and similar. This allows users to select multiple cards and perform actions such as adding/removing tags, setting due dates, and deleting cards. It also refactors tag and due date manipulation logic into a shared utility module for improved maintainability and consistency.
Bulk operations feature:
BulkOperationsToolbarcomponent, which provides a UI for bulk actions and appears when cards are selected in selection mode.Codebase refactoring and utility improvements:
card-content-utils.jsmodule, providing reusable functions such asaddTagToContent,removeTagFromContent,setDueDateInContent, andgetTagsFromContent. Existing code inApp.jsxnow uses these shared utilities.I think these changes significantly improve the user experience for managing multiple cards and while keeping code maintainability by centralizing content manipulation logic.