You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Take <!-- #TODO --> for example, it does not show in the Tag Explorer panel. Only the syntax highlighting for the tag is supported in this scenario (which may or may not be correct, depending on what the intended Foam behaviour is).
Describe the solution you'd like
I think it would be good if it could be optional to include tags within HTML comments in the Tag Explorer because I like to classify tags outside of HTML comments as public (rendered) ones, and tags inside comments as ones not necessary to be read by anyone viewing the document (tagged comments simply for the author's convenience). Optional so that it could be turned off to only browse tags which are rendered. I don't believe I've picked this habit up from anywhere else, so I'm not sure how useful others would find this. Maybe these type of tags should have some kind of name? Markup tags?
Describe alternatives you've considered
There's also a related issue regarding the overall detection of tags: The syntax highlighting works fine for -#TODO (which I'm guessing it shouldn't), but the tag doesn't shown in Tag Explorer, presumably because Foam expects whitespace before the hash symbol.
The only reason I bring this up is because is that it's possible to configure VS Code to use editor.comments.insertSpace: false so <!--#TODO--> will be the result when toggling the line into a comment post writing it (which I presume would need manual correction to include whitespace should this feature request be implemented). Maybe a specific edge case for the sequence <!--#<tag> could be considered as valid so that the user could configure the aforementioned VS Code setting as they please? I can't think of any other scenario where you'd have an intentional tag without preceding whitespace in a Markdown file.
For my use case, the alternative would be to not rely upon Foam to track these author-only type comments containing a #TODO tag, but instead on a dedicated to-do comments extension. The linked extension is flexible enough that I could continue to use the hashtag format rather than the traditional plain TODO if desired, but I still think there'd be some value from being able to track both these classifications of information using Foam only, e.g. Foam could see this: <!-- #needs-more-research: Obsidian vs Logseq? Foam increasingly looks like the most open choice. --> 🙂
Thanks for your consideration.
Foam 0.22.2
VSCodium 1.77.3
Screenshots or Videos
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Take
<!-- #TODO -->
for example, it does not show in the Tag Explorer panel. Only the syntax highlighting for the tag is supported in this scenario (which may or may not be correct, depending on what the intended Foam behaviour is).Describe the solution you'd like
I think it would be good if it could be optional to include tags within HTML comments in the Tag Explorer because I like to classify tags outside of HTML comments as public (rendered) ones, and tags inside comments as ones not necessary to be read by anyone viewing the document (tagged comments simply for the author's convenience). Optional so that it could be turned off to only browse tags which are rendered. I don't believe I've picked this habit up from anywhere else, so I'm not sure how useful others would find this. Maybe these type of tags should have some kind of name? Markup tags?
Describe alternatives you've considered
There's also a related issue regarding the overall detection of tags: The syntax highlighting works fine for
-#TODO
(which I'm guessing it shouldn't), but the tag doesn't shown in Tag Explorer, presumably because Foam expects whitespace before the hash symbol.The only reason I bring this up is because is that it's possible to configure VS Code to use
editor.comments.insertSpace: false
so<!--#TODO-->
will be the result when toggling the line into a comment post writing it (which I presume would need manual correction to include whitespace should this feature request be implemented). Maybe a specific edge case for the sequence<!--#<tag>
could be considered as valid so that the user could configure the aforementioned VS Code setting as they please? I can't think of any other scenario where you'd have an intentional tag without preceding whitespace in a Markdown file.For my use case, the alternative would be to not rely upon Foam to track these author-only type comments containing a
#TODO
tag, but instead on a dedicated to-do comments extension. The linked extension is flexible enough that I could continue to use the hashtag format rather than the traditional plainTODO
if desired, but I still think there'd be some value from being able to track both these classifications of information using Foam only, e.g. Foam could see this:<!-- #needs-more-research: Obsidian vs Logseq? Foam increasingly looks like the most open choice. -->
🙂Thanks for your consideration.
Foam 0.22.2
VSCodium 1.77.3
Screenshots or Videos
No response
The text was updated successfully, but these errors were encountered: