* Introduced FOAM_TITLE_SAFE, which is the FOAM_TITLE variable with all the invalid path characters replaced by '-'
* (out of scope) In notes explorer show item description only when name is different from note title
* Renamed commands and labels in connections panel
* renamed backlinks.ts -> connections.ts
* (out of scope) In notes explorer show item description only when name is different from note title
* Turning backlinks panel to connections panel
* Added support for filter commands
* Fixed broken imports that were driving tests nuts
* Do not register connections.* commands during test
* Refactor: improved generate link references code
* Cleaned up update-wikilink module
* update-wikilink command uses janitor code
* Moved NoteLinkDefinition code in own class, and fixed duplication error
* Renamed command
* Testing on linux only...while I figure out the issue with the other systems
* Simplified feature activation API
* Moved tree view util modules and added comments to classes
* Removed deprecated command foam-vscode.create-note-from-default-template
* Added notes explorer
* Fixed line reference in range tree items
Thanks to Wikilens extensions for the high level inspiration (and the choice for the backlink tree item icon, as I find it just perfect)
* Addresses #1184
Currently tag completion only works in the front matter if you type a `#`
character. Adding the suggested tag will then mark the tag as a comment
```markdown
---
tags: #foo #bar
---
```
Update the tag completion provider to recognize if we are in the
front-matter, by using adding two functions to utils.ts. Because the
tag completion intellisense must be summoned with either the `#`
character or the keybinding (typically `ctrl+space`), allow
for 2 outcomes
1. if the tag is prefixed in the front matter with a `#`, remove it when
substituting the tag.
2. If `ctrl-space` is used, recognize we are on the `tags: ` line and
allow for non-`#` prefaced words.
The tag provider only works on the `tags: ` within the `tags: ` key of
the frontmatter. For example
```markdown
---
title: A title
tags:
- foo
- bar
- |
```
(where `|` is the cursor) will provide suggestions for tags.
Outside the `tags:` element, suggestions will not be provided.
```markdown
---
title: A title
tags:
- foo
- bar
dates:
- 2023-01-1
- |
```
* Refactor into functions for front matter & content
Refactor the main provider method into two
sub-functions, one for front matter, one for
regular content. Add helper functions to generate
the `CompletionItems` and to find the start & end
indices of the last match to `#{tag}`.
* Show note block in panels on hover preview
* Show tag references within tag explorer
* Improved structure of view related commands
* Refactored grouped resources tree data provider and added support for placeholders filter
- Consolidated the naming of the accessory commands
- Consolidated the management of the state/context related to grouping
- Removed group-by config, simply restore the last used setting
- Added filter to only show the placeholders related to the open file
* Refreshing placeholders when changing editor and filtering by active document
* Allow for `#` alone to trigger tag completion
In #1183, I reused [HASHTAG_REGEX](83a90177b9/packages/foam-vscode/src/core/utils/hashtags.ts (L2-L3))
to validate the tag line when the `CompletionProvider` was triggered.
I wanted to prevent this:
```markdown
# This is a Markdown header
```
but using the `HASHTAG_REGEX` had the side effect of requiring an
_additional_ character to trigger the completion provider.
```markdown
1. #p <-- triggers completion
2. # <-- does not trigger
3. #_ (space) <-- does not trigger
```
both 1. and 2. should have triggered.
To fix, I use a slightly different regex that uses a negative lookahead
to ensure that the `#` is not followed by a space. I also added spec
cases to cover this situation.
* Update regex for more robust detection of tags
Update the regex used for more robust detection of tags. Replace the
negative lookahead assertion `\s` with `[ \t]` (allow for `\n`), and
add `#` to the class so that `##` is ignored.
Attempted to add the negation `^[0-9p{L}p{Emoji}p{N}-/]` to the
negative look ahead. This was to exclude items like `#$`, `#&` that
can't be tags. However my regex-fu was insufficient.
Instead, if the regex match is to a single `#`, ensure it is the
character to the left of the cursor. Example
`this is text #%|`
where the `|` represents the cursor. The `TAG_REGEX`
will match the `#` at index 13. However since the cursor is at 15, the
Completion provider will not run.
Update the tests to cover these situations and add them all to a sub-
`describe` block labeled by the bug issue number #1189
* Use regex groups to determine match position
For the case like `here is #my-tag and now # |`, where `|` is the cursor
position after a trailing space, the match on `#my-tag` would allow tag
completion at the cursor position.
Ensure that the last regexp match group covers up to the the cursor
position. This also handles the case of `#$` because the match will only
be `#`.
This commit fixes an issue in the note creation flow where a template is used. Before the fix, when a template is present, Foam would force an absolute path resolution instead of delegating that step to the note creation. After the fix this step is removed and the resolution is left to the note creation code
Instead of a generic `TAG_REGEX`, use the more specific `HASHTAG_REGEX` to identify a tag when launching tab completion.
Also add a new test case with the issue number in the test case description
