![\"Buy](\"https://cdn.buymeacoffee.com/buttons/v2/default-blue.png\")
\n"
},
{
"path": "biome.json",
"content": "{\n \"$schema\": \"https://biomejs.dev/schemas/2.0.4/schema.json\",\n \"vcs\": {\n \"enabled\": false,\n \"clientKind\": \"git\",\n \"useIgnoreFile\": true\n },\n \"files\": {\n \"ignoreUnknown\": false,\n \"includes\": [\"src/**\", \"test/**\", \"!test/mocks/**\"]\n },\n \"formatter\": {\n \"enabled\": true,\n \"indentWidth\": 4,\n \"useEditorconfig\": true\n },\n \"assist\": {\n \"actions\": {\n \"source\": {\n \"organizeImports\": \"on\"\n }\n }\n },\n \"linter\": {\n \"enabled\": true,\n \"rules\": {\n \"recommended\": true,\n \"style\": {\n \"noParameterAssign\": \"error\",\n \"useAsConstAssertion\": \"error\",\n \"useDefaultParameterLast\": \"error\",\n \"useEnumInitializers\": \"error\",\n \"useSelfClosingElements\": \"error\",\n \"useSingleVarDeclarator\": \"error\",\n \"noUnusedTemplateLiteral\": \"error\",\n \"useNumberNamespace\": \"error\",\n \"noInferrableTypes\": \"error\",\n \"noUselessElse\": \"error\"\n }\n }\n },\n \"javascript\": {\n \"formatter\": {\n \"quoteStyle\": \"double\"\n }\n }\n}\n"
},
{
"path": "docs/AppendingText.md",
"content": "# Append text anywhere\n\nYou can define a [task group](README.md#task-groups) named `text` to create a string you can append to any line of text (not just tasks).\n\nThis can be useful if you want to configure a quick append string that matches the date format you use for your tasks.\n\nAppending a date and removing matching text work in the same way for both tasks and general text, however, the appended date text is not removed if that line of text is later converted into a task.\n"
},
{
"path": "docs/README.md",
"content": "# Task Collector Configuration\n\nThis doc will give a high level overview of how Task Collector works, and its core configuration elements. \n\n- [General Options](#general-options)\n- [Task Groups](#task-groups)\n- [Menus and modals](#menus-and-modals)\n\nFor readability, we've broken some things into their own docs:\n\n- [Task Collection](TaskCollection.md)\n- [Appending text to lines (not tasks)](AppendingText.md)\n\nOther references: \n\n- [Why marks?](../README.md#why-mark)\n- [Task mark selection](../README.md#task-mark-selection)\n- [Marking tasks](../README.md#marking-tasks)\n\n---\n\n## General options\n\n- **Toggle: Task collection** \n This option enables [Task collection](TaskCollection.md). Additional settings will be available if this is enabled.\n - *default*: disabled \n\n\n- **Define task mark cycle** _(optional)_ \n Use this option to specify a string of marks that can be iterated sequentially using `(TC) Mark previous` and `(TC) Mark next` commands.\n - *default*: (empty string, disabled)\n - **Notes**:\n - `(TC) Mark previous` and `(TC) Mark next` are not registered unless or until a task mark cycle is defined.\n\n\n- **Toggle: Convert non-list lines** (✨ 1.0.4)\n Convert lines that are not tasks into tasks when you mark them.\n - *default*: disabled\n\n\n- **Skip matching sections** _(optional)_ (✨ 1.0.13)\n When collecting tasks, skip any sections that match the specified pattern.\n - *default*: (empty string, disabled)\n - **Notes**:\n - *Be careful!* Test your expression before using it. There are several [online](https://www.regextester.com/) [tools](https://regex.observepoint.com/) that can help.\n\n\n\n---\n\n## Task groups\n\nOne or more task marks can be configured together in a group.\n\n- `default` is a special group that can not be deleted. Any mark that is not included in any other group uses the default group settings.\n- `text` is a special name used for [appending text](AppendingText.md).\n\n### Task group configuration\n\n- **Group name** _(required)_ \n Each group should have a unique name. The names are significant only as an identifier.\n - **Toggle: Complete** \n Enable this toggle if this group of marks indicate [completed tasks](../README.md#completed-tasks).\n\n\n- **Task marks** _(required)_ \n Tasks are specified as a contiguous string: ` !/?r`\n - **Notes**:\n - A mark can only belong to one group. \n - A `space` is a valid character. If a space is present, `⎵` is drawn (CSS) as an eye-catcher.\n - The string will sort itself as you add characters to it.\n\n \n- **Append date to selected task(s)** _(optional)_\n - *default*: (empty string, disabled)\n - *example*: `[(]YYYY-MM-DD[)]`, results in `(2021-09-27)`\n - **Notes**:\n - When a [moment.js date format](https://momentjs.com/docs/#/displaying/format/) is specified, the current date/time will be appended to the task text.\n - Use square brackets to surround content that is not part of the format string. \n - When working with dataview-friendly annotations, for example, your format string should look something like this: `[[completion::]YYYY-MM-DD[]]`.\n - See [marking tasks](../README.md#marking-tasks)\n\n \n- **Remove text matching pattern** \n Remove text matching this [regular expression](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Regular_Expressions) from the task text. \n - *default*: (empty string, disabled)\n - *example*: `#(task|todo)` (remove #task or #todo tags)\n - **Notes**:\n - *Be careful!* Test your expression before using it. There are several [online](https://www.regextester.com/) [tools](https://regex.observepoint.com/) that can help.\n - Aside from an immediate \"undo\", this is not a reversible operation.\n - See [marking tasks](../README.md#marking-tasks)\n\n \n- **Toggle: Register '(TC) Mark with... ' command** \n Register a command _for each mark in the group_. \n - *default*: `false`\n - **Notes**:\n - Commands can be bound to hot-keys... \n\n \n- **Toggle: Add '(TC) Mark with... ' menu item** \n Register a right-click context menu item _for each mark in the group_. \n - *default*: `false`\n\n \n- **Area heading** _(if [task collection](TaskCollection.md) is enabled)_ \n Matching marked items will be inserted under the specified heading (most recent at the top). \n - *default*: (empty string, disabled)\n - **Notes**:\n - The area heading must be defined to enable collection for the group.\n - See [task collection](TaskCollection.md) for details.\n\n \n- **Toggle: Remove checkbox** _(if [task collection](TaskCollection.md) is enabled)_ \n Remove the checkbox marked tasks during the move to the configured area. \n - *default*: false\n\n---\n\n## Menus and modals\n\n- **Toggle: Prompt on checkbox click in Reading or Live preview**: \n When true, the [Task mark selection dialog](../README.md#task-mark-selection) will be opened when you click on a checkbox in Reading or Live Preview mode.\n - *default*: `false`\n - **Notes**:\n - This may conflict with a similar handler from the [Tasks](https://obsidian-tasks-group.github.io/obsidian-tasks/) plugin. Use one or the other, not both.\n\n \n- **Toggle: Add '(TC) Mark task' menu item** (✨ 0.6.4)\n Add an item to the right-click menu in edit mode to mark the task _on the current line (or within the current selection)_. It will open the [Task mark selection dialog](../README.md#task-mark-selection).\n - *default*: `false`\n\n \n- **Toggle: Add '(TC) Collect tasks' menu item** _(if [task collection](docs/../TaskCollection.md) is enabled)_ \n Add an item to the right-click menu to collect tasks in the current note.\n - *default*: `false`\n\n"
},
{
"path": "docs/TaskCollection.md",
"content": "# Task collection\n\nTask collection works on the tasks within a note. \n\nTasks that match a mark configured for collection will be gathered into the designated area of the note.\n\nThe `(TC) Collect Tasks` command or menu item triggers the following process:\n\n1. Any missing Area headings will be added to the end of the document.\n2. The document will be scanned from top to bottom to isolate discovered Area headings and their target sections.\n3. General note content is scanned from top to bottom for tasks that should be collected. Each discovered task is moved to a block of pending tasks associated with the closest matching Area header ([where do tasks go](#where-do-tasks-go)?).\n4. Collection target sections are then scanned (in order of appearance in the doc) for tasks that belong in a different section. Those are then added to the block of pending tasks for the closest matching Area header.\n5. Finally, the document is reassembled. Area headings and their target sections are placed back into the document, with the pending block for each appearing immediately under the section header (most recent will be first).\n \n \nIf you walk through the above with the following example, you should end up with the tasks in the same order:\n\n| Before | After |
|---|---|
| |