v2/examples/panic-recovery-test/README.md (3)

9-12: Add language identifier to fenced code block.

The error output code block should specify a language for proper syntax highlighting.

📝 Suggested fix

-```
+```text
 signal 11 received but handler not on signal stack
 fatal error: non-Go code set up signal handler without SA_ONSTACK flag
-```
+```

---

58-60: Add language identifier to fenced code block.

The expected output code block should specify a language for consistency.

📝 Suggested fix

-```
+```text
 ------------------------------"invalid memory address or nil pointer dereference"
-```
+```

---

73-76: Convert bare URLs to proper markdown links.

Using markdown link syntax improves readability and follows markdown best practices.

📝 Suggested fix

 ## Related
 
-- Issue: https://github.com/wailsapp/wails/issues/3965
-- Original fix PR: https://github.com/wailsapp/wails/pull/2152
+- Issue: [`#3965`](https://github.com/wailsapp/wails/issues/3965)
+- Original fix PR: [`#2152`](https://github.com/wailsapp/wails/pull/2152)

v2/examples/panic-recovery-test/frontend/src/main.js (1)

31-42: Redundant try-catch block.

The outer try-catch only catches synchronous errors, but Greet() returns a Promise. The .catch() handler already handles Promise rejections, making the outer try-catch unnecessary.

♻️ Suggested simplification

     // Call App.Greet(name)
-    try {
-        Greet(name)
-            .then((result) => {
-                // Update result with data back from App.Greet()
-                resultElement.innerText = result;
-            })
-            .catch((err) => {
-                console.error(err);
-            });
-    } catch (err) {
-        console.error(err);
-    }
+    Greet(name)
+        .then((result) => {
+            // Update result with data back from App.Greet()
+            resultElement.innerText = result;
+        })
+        .catch((err) => {
+            console.error(err);
+        });

v2/examples/panic-recovery-test/frontend/wailsjs/runtime/runtime.d.ts (2)

21-26: Minor formatting inconsistency in interface declaration.

The Screen interface has inconsistent spacing around colons compared to other interfaces (width : number vs width: number).

📝 Suggested fix

 export interface Screen {
     isCurrent: boolean;
     isPrimary: boolean;
-    width : number
-    height : number
+    width: number;
+    height: number;
 }

---

239-249: Minor formatting inconsistencies in function declarations.

A few function declarations have minor formatting issues: missing space after comma, and missing semicolons.

📝 Suggested fixes

 // [OnFileDrop](https://wails.io/docs/reference/runtime/draganddrop#onfiledrop)
 // OnFileDrop listens to drag and drop events and calls the callback with the coordinates of the drop and an array of path strings.
-export function OnFileDrop(callback: (x: number, y: number ,paths: string[]) => void, useDropTarget: boolean) :void
+export function OnFileDrop(callback: (x: number, y: number, paths: string[]) => void, useDropTarget: boolean): void;
 
 // [OnFileDropOff](https://wails.io/docs/reference/runtime/draganddrop#dragandddropoff)
 // OnFileDropOff removes the drag and drop listeners and handlers.
-export function OnFileDropOff() :void
+export function OnFileDropOff(): void;
 
 // Check if the file path resolver is available
 export function CanResolveFilePaths(): boolean;
 
 // Resolves file paths for an array of files
-export function ResolveFilePaths(files: File[]): void
+export function ResolveFilePaths(files: File[]): void;

v2/examples/panic-recovery-test/frontend/wailsjs/runtime/runtime.js (1)

59-62: Consider using modern spread syntax for clarity.

The expression [eventName].slice.call(arguments) works but is non-idiomatic. Using rest parameters or spread syntax would be clearer and more maintainable.

♻️ Suggested improvement

-export function EventsEmit(eventName) {
-    let args = [eventName].slice.call(arguments);
-    return window.runtime.EventsEmit.apply(null, args);
+export function EventsEmit(eventName, ...args) {
+    return window.runtime.EventsEmit(eventName, ...args);
 }