Closed annalinneajohansson closed 7 years ago
Have you tried clicking on the TODO icon in the bottom status bar?
Yes, I've used both that and the command list. Same response.
On Fri, 24 Mar 2017, 01:23 pmcoz, notifications@github.com wrote:
Have you tried clicking on the TODO icon in the bottom status bar?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/kantlove/vscode-todo-parser/issues/58#issuecomment-288899182, or mute the thread https://github.com/notifications/unsubscribe-auth/ABHF41XMSHQFn0lLiNYj1Q2DD22wg3aoks5rowzmgaJpZM4MmRK7 .
I also tried with clearing the console output, restarting Visual Studio Code and un- and reinstallning the extension.
Hi @annalinneajohansson, Can you try switching to another file and switch back?
No luck; now I'm instead getting No TODOs found.
I've tried a couple of different markers to, but it doesn't detect any of them: @todo, @TODO, TODO and TODO:
I'm on Ubuntu 16.10, GNOME 3.20.4 in case that makes any difference @kantlove
Found the issue: I'd added my TODO:s in docblocks multiline DocComments as so:
/**
* TODO To do description
*/
and it doesn't seem to detect them when I do so.
Changing the above to
/** TODO To do description */
returns it as expected in the console.
Can I know what language you are using?
The files I've tested are in PHP
@annalinneajohansson thank you for reporting this 👍
The extension cannot recognize multi-line comments starting with /**
(2 asterisks)
But this is fixed in v1.8.10
Love the extension but it seems to be stuck in returning a cached response for me. I'm getting the todo I first added, but after updating the file in question with several more (and also removing the first todo), I'm still getting that first todo returned (and none of the new ones).