Add multiline-comment-style lint rule and fix violations

Enable multiline-comment-style with starred-block to require JSDoc-style
block comments with content on separate lines from the opening delimiter.
Auto-fix existing violations across the codebase.

Fixes #5899

Co-authored-by: Daniel Imms <Tyriar@users.noreply.github.com>
This commit is contained in:
Cursor Agent
2026-05-26 20:15:55 +00:00
co-authored by Daniel Imms
parent 1a67b6f4b3
commit 4ec85e67ba
138 changed files with 3040 additions and 1837 deletions
+9 -5
View File
@@ -180,9 +180,11 @@ function startServer(): void {
}
const send = (USE_BINARY ? bufferUtf8 : buffer)(ws, 3, 262144);
// WARNING: This is a naive implementation that will not throttle the flow of data. This means
// it could flood the communication channel and make the terminal unresponsive. Learn more about
// the problem and how to implement flow control at https://xtermjs.org/docs/guides/flowcontrol/
/*
* WARNING: This is a naive implementation that will not throttle the flow of data. This means
* it could flood the communication channel and make the terminal unresponsive. Learn more about
* the problem and how to implement flow control at https://xtermjs.org/docs/guides/flowcontrol/
*/
term.onData(function(data) {
try {
send(data as string & Buffer);
@@ -209,8 +211,10 @@ function startServer(): void {
app.listen(port, host, 0);
}
// HACK: There is an EPIPE error thrown when reloading a page. This only seems to happen on Windows
// and it's unclear why it happens. Suppressing the error here since this is just the demo server.
/*
* HACK: There is an EPIPE error thrown when reloading a page. This only seems to happen on Windows
* and it's unclear why it happens. Suppressing the error here since this is just the demo server.
*/
process.on('uncaughtException', (error) => {
if (process.platform === 'win32' && error.message === 'read EPIPE') {
return;