Closed vsfeedback closed 2 years ago
Actually, moving back to azure devops side.
@NTaylorMullen
Actually, moving back to azure devops side.
Hi, what does that mean, please? Seems like there is no progess on this issue. And also I am still receiving responses in the original Visual Studio Feedback post from your tester who says that is not able to reproduce the issue because they are doing a different thing than what I reported (such a simple example) (happened now two times in a row).
@janseris Sorry, that just means that the team that's responsible for the bug isn't here on GitHub.
As for there not being a ton of traction, I followed up and that team is currently addressing higher hitcount issues. I'm a it surprised that not more folks have ran into this problem to be totally frank; however, definitely slam that upvote button in the Visual Studio Feedback post (they use that number to help prioritize)
This issue has been moved from a ticket on Developer Community.
[severity:It bothers me. A fix would be nice]
Result of pressing ENTER key:
Expected result: no /// at the beginning of the line
Code:
Original Comments
Feedback Bot on 5/25/2022, 00:28 AM:
(private comment, text removed)
Original Solutions
(no solutions)