Open shiroyasha opened 4 months ago
I mostly use commenting to disable parts of the code that are not yet passing the tests, and then slowly uncomment the parts as they are implemented.
However, when I hit gc inside of a React code block, it comments it out with regular // javascript comments. This is not correct React comments.
gc
//
function Example(props) { const value = "some value"; return <div> <ul> <li>Hello</li> </ul> </div> }
function Example(props) { const value = "some value"; return <div> // <ul> <--- this comment style is breaking react code // <li>Hello</li> // </ul> </div> }
Ideally, Neovim would know that I'm in that context, and use {/* */} comments.
{/* */}
function Example(props) { const value = "some value"; return <div> {/* <ul> */} {/* <li>Hello</li> */} {/* </ul> */} </div> }
My solution so far is to either:
I mostly use commenting to disable parts of the code that are not yet passing the tests, and then slowly uncomment the parts as they are implemented.
However, when I hit
gc
inside of a React code block, it comments it out with regular//
javascript comments. This is not correct React comments.Ideally, Neovim would know that I'm in that context, and use
{/* */}
comments.My solution so far is to either: