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
{{ message }}
This repository has been archived by the owner on Dec 25, 2023. It is now read-only.
Hi. I was about to file a bug, but wanted to ask first.
Coming from VSCode, I'm used to CMD+/ commenting out the current line or selection—not in the JSX portion of the code—by appending // myCode() to it. But in Nova I'm instead getting { /* myCode() / }. It seems like it doesn't distinguish between JSX and the rest of the code?
Exacerbating this problem is that Prettier (I think) then sees that 'comment' and formats it across multiple lines. Selecting this expanded 'comment' and hitting CMD+/ should at least uncomment it, but it actually re-comments it, which breaks the code.
Moreover some linter somewhere then complains that I have an empty object in my code.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi. I was about to file a bug, but wanted to ask first.
Coming from VSCode, I'm used to CMD+/ commenting out the current line or selection—not in the JSX portion of the code—by appending
// myCode()
to it. But in Nova I'm instead getting{ /* myCode() / }
. It seems like it doesn't distinguish between JSX and the rest of the code?Exacerbating this problem is that Prettier (I think) then sees that 'comment' and formats it across multiple lines. Selecting this expanded 'comment' and hitting CMD+/ should at least uncomment it, but it actually re-comments it, which breaks the code.
Moreover some linter somewhere then complains that I have an empty object in my code.
Is this just happening to me?
Beta Was this translation helpful? Give feedback.
All reactions