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
I like the idea of TSDoc and prefer to use the “official” syntax (with the help of linters). However, I often find myself tweaking some doc content to adhere to editor rendering (I use WebStorm (JetBrains/IntelliJ) primarily, but colleagues use VS Code).
So, what focus on editor integration exists in 2023?
For example, should we open issues to “fix” rendering issues. (I just came across issues with @link (finalized I think?) and @see (not finalized), which prompted me to ask this question.)
The text was updated successfully, but these errors were encountered:
I like the idea of TSDoc and prefer to use the “official” syntax (with the help of linters). However, I often find myself tweaking some doc content to adhere to editor rendering (I use WebStorm (JetBrains/IntelliJ) primarily, but colleagues use VS Code).
So, what focus on editor integration exists in 2023?
For example, should we open issues to “fix” rendering issues. (I just came across issues with
@link
(finalized I think?) and@see
(not finalized), which prompted me to ask this question.)The text was updated successfully, but these errors were encountered: