Ignore a eslint false positive

portal/src/ErrorBoundSuspense.tsx

@@ -7,21 +7,16 @@ import React, {
   useState,
   useEffect,
 } from "react";
-import { ErrorBoundary, ErrorBoundaryProps } from "@sentry/react";
+import { ErrorBoundary, FallbackRender } from "@sentry/react";
 
 export interface ErrorBoundSuspenseProps {
-  errorBoundaryFallback: NonNullable<ErrorBoundaryProps["fallback"]>;
+  errorBoundaryFallback: FallbackRender;
   suspenseFallback: SuspenseProps["fallback"];
   factory: () => Promise<{ default: React.ComponentType<any> }>;
   children: (Component: React.ComponentType<any>) => React.ReactNode;
 }
 
-export interface ErrorBoundaryFallbackProps {
-  error: unknown;
-  componentStack: string;
-  eventId: string;
-  resetError(): void;
-}
+export type ErrorBoundaryFallbackProps = Parameters<FallbackRender>[0];
 
 const extractImportArgRegex = /import\(["']([-_./a-zA-Z0-9]+)["']\)/;
 

portal/src/FlavoredErrorBoundSuspense.tsx

@@ -17,6 +17,14 @@ export interface FlavoredErrorBoundSuspenseProps {
 function FallbackComponent(
   props: ErrorBoundaryFallbackProps
 ): React.ReactElement<any, any> {
+  // The definition of resetError is
+  //   resetError(): void;
+  // instead of
+  //   resetError: () => void;
+  // This makes TypeScript think it is method that could access this.
+  // But I think that is just a mistake in the type definition.
+  // So it should be safe to ignore.
+  // eslint-disable-next-line @typescript-eslint/unbound-method
   const { resetError } = props;
   const onClick = useCallback(
     (e: React.MouseEvent<unknown>) => {