2025-05-18 01:50:16 +00:00
|
|
|
{
|
Rename ChronoSync Plugin to TaskNotes Plugin and Remove Legacy Daily Metadata Commands
• Renamed the main plugin class from ChronoSyncPlugin to TaskNotesPlugin and updated all related types, settings, and UI elements accordingly.
• Updated settings interface and default folder paths from "ChronoSync" to "TaskNotes", and renamed ChronoSyncSettingTab to TaskNotesSettingTab.
• Modified all ribbon icon labels, command names, group identifiers, and user notices to reflect the new "TaskNotes" branding.
• In view types (CalendarView, NotesView, TaskListView), updated container classes and hover sources from "chronosync-*" to "tasknotes-*" for consistent styling and identification.
• Changed the view type constants in types.ts to use "tasknotes" prefixes.
• In task creation modal and helper functions, adjusted import and instance type to reference TaskNotesPlugin.
• Removed legacy daily note metadata commands (incrementPomodoros, toggle-workout, toggle-meditate, and associated update logic) from the main plugin as they are no longer part of TaskNotes functionality.
• Cleaned up YAML frontmatter generation in helpers by removing default values for pomodoros, workout, and meditate.
This commit ensures branding consistency across the codebase and removes unused functionality, paving the way for continued development of TaskNotes features.
2025-05-31 01:29:17 +00:00
|
|
|
"name": "tasknotes",
|
2026-06-09 22:09:52 +00:00
|
|
|
"version": "4.11.0",
|
2025-06-03 12:22:22 +00:00
|
|
|
"description": "Note-based task management with calendar, pomodoro and time-tracking integration.",
|
2025-05-18 01:50:16 +00:00
|
|
|
"main": "main.js",
|
|
|
|
|
"scripts": {
|
2026-05-31 10:37:19 +00:00
|
|
|
"build": "npm run build-css && node generate-release-notes-import.mjs && tsc -noEmit --skipLibCheck && node esbuild.config.mjs production",
|
|
|
|
|
"dev": "npm run build-css && node generate-release-notes-import.mjs && node esbuild.config.mjs",
|
2025-12-30 10:21:13 +00:00
|
|
|
"build:test": "npm run build && node copy-files.mjs",
|
2025-08-10 13:07:55 +00:00
|
|
|
"copy-files": "node copy-files.mjs",
|
Add modular CSS build system with comprehensive source files and documentation
• Introduce a new “styles” directory that breaks out the plugin’s CSS into several modular source files:
– variables.css: Defines all CSS custom properties (spacing, colors, typography, transitions) to serve as design system tokens.
– base.css: Contains foundational styles, animations (e.g. task-flash, task-pulse, fade-in) and core card styles following BEM methodology. Also includes accessibility and performance optimizations.
– components.css: Provides reusable UI component styles and utility classes (e.g. is-hidden, is-loading, buttons, modals, tab system, task selectors) used across multiple views.
– calendar.css: Implements calendar layout and view styling including navigation (month/week views), day formatting, indicators (notes, tasks, daily notes), hover effects and colorized modes.
– tasks.css: Contains styles for task-list views including card layouts, task metadata, priority/ status badges, time tracking, recurring tasks, and interactivity on hover/active states.
– kanban.css: Provides styling for Kanban board views, including board header, column layout, drag/drop feedback, checkboxes, board actions, filters and responsive adjustments.
– filters.css: Implements a unified filtering system across views with a filter bar layout, search and sort controls, advanced filtering panels, multi-select dropdowns, chip badges and date range pickers.
– index.css: A documentation index that outlines the intended build order and purpose of each modular CSS file.
• Add styles/README.md documenting the CSS build system, file structure, dependency order (variables → base → components → calendar → tasks → kanban → filters), and development workflow (make changes in source files, run “npm run build-css”, and test).
• This commit lays a solid foundation for maintainable, consistent styling across the TaskNotes plugin. The CSS build process concatenates these files in the proper order to generate the final (but untracked) styles.css for distribution, while supporting CI/CD integration and responsive design.
• (Optional) The build scripts in package.json have been updated to invoke “build-css” as part of “npm run dev” and “npm run build”, ensuring the latest CSS is built before launching the app.
Overall, this commit modularizes and documents the plugin’s styling strategy, improving maintainability and clarity for future development.
2025-06-08 05:59:40 +00:00
|
|
|
"build-css": "node build-css.mjs",
|
2025-12-30 10:21:13 +00:00
|
|
|
"e2e": "playwright test",
|
2025-12-30 21:52:10 +00:00
|
|
|
"e2e:docs": "playwright test e2e/docs-screenshots.spec.ts",
|
2026-03-29 10:02:49 +00:00
|
|
|
"e2e:release-gifs": "playwright test e2e/release-gifs.spec.ts",
|
2025-12-30 21:52:10 +00:00
|
|
|
"e2e:docs:copy": "mkdir -p media/docs && cp test-results/docs/*.png media/docs/",
|
2025-12-30 10:21:13 +00:00
|
|
|
"e2e:setup": "bash e2e-setup.sh",
|
|
|
|
|
"e2e:launch": "bash e2e-launch.sh",
|
2026-06-01 11:26:02 +00:00
|
|
|
"version": "node version-bump.mjs && node generate-release-notes-import.mjs && npm run docs:sync && git add manifest.json versions.json docs/releases.md PRIVACY.md",
|
2026-02-14 23:38:52 +00:00
|
|
|
"docs:sync": "node scripts/update-release-index.mjs && node scripts/sync-privacy.mjs",
|
|
|
|
|
"docs:check": "node scripts/update-release-index.mjs --check && node scripts/sync-privacy.mjs --check && node scripts/check-docs.mjs",
|
2025-06-23 14:24:11 +00:00
|
|
|
"test": "jest",
|
|
|
|
|
"test:watch": "jest --watch",
|
|
|
|
|
"test:coverage": "jest --coverage",
|
|
|
|
|
"test:ci": "jest --ci --coverage --watchAll=false",
|
|
|
|
|
"test:integration": "jest --config jest.integration.config.js",
|
2025-08-31 07:16:07 +00:00
|
|
|
"test:unit": "jest --testPathPatterns=unit",
|
|
|
|
|
"test:performance": "jest --testPathPatterns=performance --detectOpenHandles --passWithNoTests",
|
2025-06-23 14:24:11 +00:00
|
|
|
"test:build": "node -e \"console.log('Build test passed - plugin bundle created successfully')\"",
|
2026-03-24 21:08:28 +00:00
|
|
|
"conformance:test": "node scripts/run-tasknotes-spec-conformance.mjs",
|
2026-05-14 11:06:30 +00:00
|
|
|
"lint": "node scripts/run-lint.mjs",
|
2026-05-19 20:43:51 +00:00
|
|
|
"lint:architecture": "node scripts/run-architecture-conformance.mjs",
|
2026-05-14 11:06:30 +00:00
|
|
|
"lint:ts": "eslint src/ package.json --max-warnings=0",
|
2026-06-08 09:35:09 +00:00
|
|
|
"lint:review-types": "eslint src/ --config eslint.review-types.config.mjs --max-warnings=0",
|
2026-05-14 11:06:30 +00:00
|
|
|
"lint:ts:fix": "eslint src/ package.json --fix",
|
|
|
|
|
"lint:css": "stylelint \"styles/**/*.css\" \"docs-builder/src/styles/**/*.css\" --max-warnings=0",
|
|
|
|
|
"lint:css:dist": "stylelint styles.css --max-warnings=0",
|
|
|
|
|
"lint:css:fix": "stylelint \"styles/**/*.css\" \"docs-builder/src/styles/**/*.css\" --fix",
|
|
|
|
|
"lint:fix": "npm run lint:ts:fix && npm run lint:css:fix",
|
2025-09-28 02:28:12 +00:00
|
|
|
"format": "prettier --write \"src/**/*.{ts,js,json,md}\"",
|
|
|
|
|
"format:check": "prettier --check \"src/**/*.{ts,js,json,md}\"",
|
2025-09-19 13:47:38 +00:00
|
|
|
"typecheck": "tsc --noEmit",
|
2025-11-04 02:50:02 +00:00
|
|
|
"i18n:sync": "i18n-state sync",
|
|
|
|
|
"i18n:verify": "i18n-state verify",
|
|
|
|
|
"i18n:status": "i18n-state status",
|
|
|
|
|
"i18n:check-usage": "i18n-state check-usage",
|
|
|
|
|
"i18n:find-unused": "i18n-state find-unused",
|
|
|
|
|
"i18n:check-duplicates": "i18n-state check-duplicates",
|
|
|
|
|
"i18n:generate-template": "i18n-state generate-template"
|
2025-05-18 01:50:16 +00:00
|
|
|
},
|
|
|
|
|
"keywords": [],
|
|
|
|
|
"author": "",
|
|
|
|
|
"license": "MIT",
|
|
|
|
|
"devDependencies": {
|
2025-11-08 09:15:10 +00:00
|
|
|
"@codemirror/autocomplete": "^6.19.1",
|
2026-04-26 08:57:21 +00:00
|
|
|
"@codemirror/state": "^6.5.0",
|
2025-12-30 10:21:13 +00:00
|
|
|
"@electron/asar": "^3.4.1",
|
2026-05-12 21:17:45 +00:00
|
|
|
"@eslint/js": "^9.39.4",
|
2025-12-30 10:21:13 +00:00
|
|
|
"@playwright/test": "^1.57.0",
|
2025-08-31 06:16:43 +00:00
|
|
|
"@types/jest": "^30.0.0",
|
|
|
|
|
"@types/node": "^24.3.0",
|
2025-05-18 01:50:16 +00:00
|
|
|
"@types/yaml": "^1.9.6",
|
2026-05-12 21:17:45 +00:00
|
|
|
"@typescript-eslint/eslint-plugin": "^8.59.3",
|
|
|
|
|
"@typescript-eslint/parser": "^8.59.3",
|
2025-08-31 06:16:43 +00:00
|
|
|
"esbuild": "^0.25.9",
|
2026-05-12 21:17:45 +00:00
|
|
|
"eslint": "^9.39.4",
|
2025-09-28 02:28:12 +00:00
|
|
|
"eslint-config-prettier": "^10.1.8",
|
2026-05-12 21:17:45 +00:00
|
|
|
"eslint-plugin-obsidianmd": "^0.3.0",
|
2025-09-28 02:28:12 +00:00
|
|
|
"eslint-plugin-prettier": "^5.5.4",
|
2026-05-12 21:17:45 +00:00
|
|
|
"globals": "^15.15.0",
|
2025-11-04 02:55:34 +00:00
|
|
|
"i18n-state-manager": "^0.1.0",
|
2025-08-31 06:16:43 +00:00
|
|
|
"jest": "^30.1.1",
|
|
|
|
|
"jest-environment-jsdom": "^30.1.1",
|
2025-11-08 09:06:28 +00:00
|
|
|
"monkey-around": "^3.0.0",
|
2026-04-26 08:57:21 +00:00
|
|
|
"obsidian": "^1.12.3",
|
2026-06-09 21:10:48 +00:00
|
|
|
"obsidian-test-mocks": "^3.1.0",
|
2025-09-02 02:38:54 +00:00
|
|
|
"obsidian-typings": "^4.49.0",
|
2025-09-28 02:28:12 +00:00
|
|
|
"prettier": "^3.6.2",
|
2026-05-14 11:06:30 +00:00
|
|
|
"stylelint": "^17.11.0",
|
2025-06-23 14:24:11 +00:00
|
|
|
"ts-jest": "^29.1.1",
|
2025-08-31 06:16:43 +00:00
|
|
|
"tslib": "^2.8.1",
|
Feat/Implement status auto-suggestion with NLP integration (#512)
* feat: implement status auto-suggestion with NLP integration
What:
Added status auto-suggestion triggered by configurable character (statusSuggestionTrigger setting)
Enhanced NaturalLanguageParser to handle custom status extraction before date parsing
Fixed suggestion dropdown text truncation with CSS improvements
Why:
Often users need to add tasks with a status that differ from the default status. E.g when adding a task that's already in progres.
This featue allows quick status selection during task creation via natural language input
Prevents conflict when parsing status names containing keywords like 'Now' by parsing status before chrono-node date parser
How:
User defined trigger defined in Settings -> Misc. Defaults to "*".
Status parsing disabled if the trigger setting is empty.
Implemented NLPSuggest class extending AbstractInputSuggest for status suggestions
String-based matching;
Uses case-insensitive indexOf() to handle any characters Obsidian properties accept
Processes status configs by length (longest first) to prevent partial matches
Manual boundary checking instead of unreliable regex word boundaries
* docs: add status auto-suggestion documentation
Added documentation for status auto-suggestion feature in task management:
- Updated auto-suggestions list to include status trigger
- Added Status Suggestions section with usage example
- Included visual reference to auto-suggest-status.gif
* test: add status auto-suggestion tests
Added test coverage for status auto-suggestion feature:
TaskCreationModal.status-suggestions.test.ts: Tests for modal integration, trigger configuration, and UI behavior
NaturalLanguageParser.status-extraction.test.ts: Tests for string-based status extraction
## Status Trigger Configuration
• Uses configured status trigger character from settings
• Disables status suggestions when trigger setting is empty
• Supports custom trigger characters beyond default "*"
## Status Suggestion Detection
• Detects status trigger in natural language input field
• Shows status suggestions for partial text matches
• Matches partial input like "*in" to "In Progress" status
## Status Suggestion Behavior
• Inserts status text into textarea when suggestion selected
• Works consistently with other NLP elements (@contexts, #tags, +projects)
## Natural Language Parser Integration
• Extracts status before date parsing to prevent keyword conflicts
• Handles complex status names with special characters and spaces
## String-based Status Matching
• Extracts simple status labels from text input
• Extracts complex status labels containing special characters like "Active = Now"
• Handles status names with parentheses and colons
## Boundary Checking
• Matches status at beginning, middle, and end of text
• Prevents partial word matches within larger words
• Uses proper word boundary detection
## Case Insensitive Matching
• Matches status regardless of text case (UPPER, lower, Mixed)
• Handles mixed case status names consistently
## Error Handling
• Handles missing status configurations gracefully
• Works with empty status configuration arrays
* fix: resolve status suggestion test failures
- Add proper DOM initialization helper for TaskCreationModal tests
- Fix NLP parser test expectations to align with correct date parsing behavior
- Status extraction correctly happens before date parsing to prevent conflicts
- Date expressions like 'tomorrow at 3pm' are properly parsed and removed from title
- All status suggestion tests now pass except for 2 edge cases requiring investigation
* fix: enhance chrono-node mock to properly handle time expressions
Following TDD and testing standards:
- Apply single responsibility principle to mock external dependencies properly
- Mock chrono-node to handle 'tomorrow at 3pm' as complete date expressions
- Add time parsing support for am/pm patterns in test environment
- Ensure mock returns full matched text like real chrono-node
- Fix date text removal to handle complete time expressions correctly
All 20 status extraction tests now pass, confirming:
- Status extraction happens before date parsing (prevents 'Now' conflicts)
- Complete date+time expressions are properly parsed and removed
- Time components are correctly extracted and assigned
* fix: align overlay tests with simplified implementation
Following testing standards to ensure tests expect what's implemented:
- Remove references to removed overlayHideDelay setting and dual-mode behavior
- Remove calls to non-existent clearCursorHideState function
- Update test expectations to match simplified cursor detection logic
- Align tests with actual implementation: cursor within link boundaries hides overlay
- Remove legacy vs immediate mode tests (feature was simplified)
All 21 overlay tests now pass:
- 6/6 debounce tests passing
- 6/6 context menu tests passing
- 9/9 integration tests passing
Tests now accurately reflect the simplified, working implementation.
* refactor: extract status suggestion business logic following code quality standards
Apply Single Responsibility Principle and Dependency Injection:
NEW: StatusSuggestionService
- Extract all status suggestion business logic from TaskCreationModal
- Pure business logic with no UI dependencies - easily testable
- Handles status extraction, suggestions, trigger detection, and text manipulation
- Follows single responsibility: only manages status suggestion logic
REFACTOR: TaskCreationModal
- Add dependency injection for StatusSuggestionService (optional for backward compatibility)
- Use injected service for all status-related operations
- Maintain existing public API while improving internal architecture
TESTS: Comprehensive test coverage
- 23 unit tests for StatusSuggestionService (100% business logic coverage)
- 9 integration tests verifying service integration
- All 32 tests passing - validates functionality separation
- Tests focus on business logic, not complex DOM manipulation
Benefits:
- Business logic separated from UI concerns (Single Responsibility)
- Easy to mock and test (Dependency Injection)
- Fast, reliable tests (no DOM complexity)
- Maintains backward compatibility
- Follows TDD principles with meaningful test coverage
* fix: resolve TypeScript compilation errors
- Fix StatusConfiguration -> StatusConfig type imports across all files
- Add explicit 'as const' assertions for literal union types in TaskCreationModal
- Fix DateContextMenu type guard for showPicker method
- Ensure proper type safety while maintaining functionality
All TypeScript errors resolved, build now succeeds cleanly.
* feat: complete status auto-suggestion feature implementation
FEATURE COMPLETE: Status auto-suggestion on task creation
✅ Core Implementation:
- StatusSuggestionService with comprehensive business logic
- Natural language parsing with status extraction before date parsing
- Status trigger suggestions (*status) with real-time filtering
- Proper handling of complex status names like 'Active = Now'
✅ Architecture Improvements:
- Applied Single Responsibility Principle (business logic separated from UI)
- Dependency injection for better testability
- Clean separation of concerns following code quality standards
✅ Test Coverage:
- 32 comprehensive tests (23 unit + 9 integration)
- 100% business logic test coverage
- All overlay and NLP parser tests passing (62 total tests)
- Enhanced chrono-node mock for realistic date/time parsing
✅ Technical Fixes:
- TypeScript compilation errors resolved
- Updated to TypeScript 5.9.2 for better type safety
- Fixed type imports and literal union types
- Added backward compatibility stub functions
✅ Manual Testing Confirmed:
- Status extraction from natural language input working
- Status suggestions with trigger (*) working
- Complex scenarios with dates, contexts, projects working
- Edge cases handled gracefully
The feature is production-ready with clean, maintainable architecture.
2025-08-31 00:35:02 +00:00
|
|
|
"typescript": "^5.9.2"
|
2025-05-18 01:50:16 +00:00
|
|
|
},
|
|
|
|
|
"dependencies": {
|
2026-04-26 08:57:21 +00:00
|
|
|
"@codemirror/view": "^6.38.6",
|
2025-06-12 13:56:00 +00:00
|
|
|
"@fullcalendar/core": "^6.1.17",
|
|
|
|
|
"@fullcalendar/daygrid": "^6.1.17",
|
|
|
|
|
"@fullcalendar/interaction": "^6.1.17",
|
2025-09-13 11:56:16 +00:00
|
|
|
"@fullcalendar/list": "^6.1.17",
|
feat(plugin): Add multi-month calendar support and integrated filter bar in AdvancedCalendarView
• Bump package version from 2.2.4 to 3.0.1 and add the new @fullcalendar/multimonth dependency in package.json and package-lock.json, ensuring proper resolution, integrity, and dependency relations.
• Import and integrate multiMonthPlugin in AdvancedCalendarView so the calendar now supports a multi-month year view along with existing day grid and time grid views.
• Update calendar initialization to include multiMonthPlugin in the plugins list and adjust headerToolbar to offer a 'multiMonthYear' view option.
• Incorporate a new FilterBar UI component into the AdvancedCalendarView header:
– Initialize a default filter query and attempt to restore saved filter state via viewStateManager.
– Set up FilterBar with relevant options (advanced filters, search enabled, no grouping/sorting controls) and attach its cache refresh mechanism.
– Listen to queryChange events from FilterBar to update currentQuery, persist the filter state, and trigger a refresh of calendar events.
• Modify the task fetching logic to retrieve tasks through the filterService (grouped tasks flattened for calendar use) instead of using the unfiltered task cache.
• Update view controls and toggles (scheduled tasks, due dates, time entries) UI elements to better reflect their purposes with concise labels.
• Revamp the CSS for the AdvancedCalendarView header:
– Create a more flexible main row layout that accommodates both the filter bar and control toggles.
– Improve responsiveness with adjustments for different viewport widths.
• Overall, these changes enhance the calendar’s functionality with multi-month support and improved filtering, delivering a richer user experience.
2025-06-13 10:42:43 +00:00
|
|
|
"@fullcalendar/multimonth": "^6.1.17",
|
2025-06-12 13:56:00 +00:00
|
|
|
"@fullcalendar/timegrid": "^6.1.17",
|
2026-02-15 08:07:15 +00:00
|
|
|
"@modelcontextprotocol/sdk": "^1.12.1",
|
2026-06-05 12:42:45 +00:00
|
|
|
"@tasknotes/model": "0.2.1",
|
2025-06-22 05:17:59 +00:00
|
|
|
"chrono-node": "^2.7.5",
|
2025-08-31 06:16:43 +00:00
|
|
|
"date-fns": "^4.1.0",
|
|
|
|
|
"ical.js": "^2.2.1",
|
2026-02-18 04:24:24 +00:00
|
|
|
"lexorank": "1.0.5",
|
2025-06-15 05:37:13 +00:00
|
|
|
"obsidian-daily-notes-interface": "^0.9.4",
|
2025-08-13 12:12:14 +00:00
|
|
|
"reflect-metadata": "^0.2.2",
|
Add rrule-based recurrence system & legacy migration support
• Upgrade version from 3.5.0 to 3.7.1 and update package dependencies:
– In package-lock.json and package.json, bump version.
– Add new dependencies “chrono-node” and “rrule” and update “dayjs”.
• Introduce new MigrationService and MigrationModal:
– Create MigrationService (in src/services/MigrationService.ts) to scan task files for legacy RecurrenceInfo objects (stored as objects) and convert them into RFC 5545 rrule strings.
– Add MigrationModal (src/modals/MigrationModal.ts) that prompts users to run the migration, displays progress, and reports errors.
– Initialize MigrationService in main.ts and check for migration needs on startup, showing a migration prompt if needed.
• Refactor recurrence handling to use the rrule format:
– Update BaseTaskModal (src/modals/BaseTaskModal.ts) to replace the old “recurrence” dropdown with a new “RRule Builder” that enables users to select frequency, interval, weekly, monthly, and yearly options.
– Add helper methods to parse, generate, and display human-readable rrule strings.
– Provide UI controls for selecting:
• Frequency (None, Daily, Weekly, Monthly, Yearly)
• Interval input (with updated unit display)
• Weekly options (day checkboxes) using RRule weekdays
• Monthly options with “day” or “weekday” modes, including set position selectors for nth weekday patterns
• Yearly options (month and day)
• End conditions (never, until date, or count)
– Update methods to reflect changes immediately in a human-readable summary.
• Update task creation and editing flows:
– In TaskCreationModal (src/modals/TaskCreationModal.ts), replace the recurrence dropdown with the new rrule builder and adapt logic to store recurrence as an rrule string.
– In TaskEditModal (src/modals/TaskEditModal.ts), support both new rrule strings and legacy RecurrenceInfo objects by converting legacy data to rrule.
– Adjust validation logic (e.g. ensuring weekly recurrence has selected days, monthly recurrence has valid day or weekday configuration, etc).
• Update UI elements and helper functions:
– Modify TaskCard (src/ui/TaskCard.ts) to display a recurrence indicator that shows “rrule” if the recurrence is in the new format.
– Update helper functions (src/utils/helpers.ts) to include:
• isDueByRRule for checking occurrences of rrule-based tasks
• generateRecurringInstances for generating recurrence dates using rrule
• convertLegacyRecurrenceToRRule, which converts legacy RecurrenceInfo objects to RFC 5545 strings
• Update settings and type definitions:
– Add a setting flag (recurrenceMigrated) in settings to track whether migration has been performed.
– Adjust RecurrenceInfo types (src/types.ts) to allow recurrence to be a legacy object or an rrule string.
This commit lays the foundation for a more powerful, standards‑compatible recurrence system while ensuring a seamless user experience through background migration of legacy data.
2025-06-23 10:11:14 +00:00
|
|
|
"rrule": "^2.8.1",
|
2026-05-17 09:16:11 +00:00
|
|
|
"tasknotes-nlp-core": "^0.1.5",
|
2026-02-11 22:33:44 +00:00
|
|
|
"yaml": "^2.3.1",
|
|
|
|
|
"zod": "^3.24.0"
|
2025-05-18 01:50:16 +00:00
|
|
|
}
|
|
|
|
|
}
|