Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pressing enter does not continue docblock #94

Open
ianmaddox opened this issue Apr 16, 2023 · 2 comments
Open

Pressing enter does not continue docblock #94

ianmaddox opened this issue Apr 16, 2023 · 2 comments
Labels

Comments

@ianmaddox
Copy link

Describe the bug
Pressing enter inside a docblock does not continue the docblock. The asterisk is not printed and the cursor moves to the beginning of the line as if it is outside a docblock.

To Reproduce

  1. Start a docblock with /** and press Enter
  2. The cursor is now inside a docblock template. Type some text and press Enter
  3. Notice that the cursor has moved to the beginning of the line and no asterisk was created

docblock not continuing

Expected behavior
A newline and " * " is printed with my cursor at the end of the newly created line.

Code Snippet

/**
  * I'm going to press enter>
Oops, I got a new line with no padded asterisk
  */

Enviroment (please complete the following information):

  • OS: Windows
  • Version 11
  • Language(s) JavaScript
@ianmaddox ianmaddox added the bug label Apr 16, 2023
@jeremyvii
Copy link
Owner

jeremyvii commented May 11, 2023

I am not able to replicate this issue, although I am on Ubuntu rather than Windows. It may be a bit before I can test on a Windows machine.

Do you have any other extensions installed?

@ianmaddox
Copy link
Author

Yes, though I recently went through the process of disabling every plugin and re-enabling them one by one. I wasn't testing for this problem in particular, but I did notice that the problem persisted even with everything turned off including vs-dockblockr and then went away once I'd enabled some unknown combination of extensions. Before I embark on another round of extension disabling, I should check if the problem is configuration. I have no idea how to check the DB continuation string setting to confirm this theory. Do you know where I should look?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants