Modified the ID generation logic in 'add-task.js' to calculate the next task ID based on the highest ID within the specified tag, rather than globally across all tags. This fixes a critical bug where creating a task in a new tag would result in a high, non-sequential ID, such as ID 105 for the first task in a tag.
6 lines
130 B
JSON
6 lines
130 B
JSON
{
|
|
"currentTag": "gezo",
|
|
"lastSwitched": "2025-06-13T04:23:16.760Z",
|
|
"branchTagMapping": {},
|
|
"migrationNoticeShown": true
|
|
} |