lint_output.txt


> commdesk-desktop@0.1.0 lint
> eslint .


C:\Users\itzza\CommDesk\src\Component\ui\DropDown.tsx
  31:7  error  Error: Calling setState synchronously within an effect can trigger cascading renders

Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.

Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).

C:\Users\itzza\CommDesk\src\Component\ui\DropDown.tsx:31:7
  29 |   useEffect(() => {
  30 |     if (value !== undefined) {
> 31 |       setSelected(value);
     |       ^^^^^^^^^^^ Avoid calling setState() directly within an effect
  32 |       return;
  33 |     }
  34 |     setSelected((prev) => (prev && options.includes(prev) ? prev : (options[0] ?? "")));  react-hooks/set-state-in-effect

C:\Users\itzza\CommDesk\src\Component\ui\Form.tsx
  10:42  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any
  28:47  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any

C:\Users\itzza\CommDesk\src\Component\ui\SearchableDropdown.tsx
  42:7  error  Error: Calling setState synchronously within an effect can trigger cascading renders

Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.

Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).

C:\Users\itzza\CommDesk\src\Component\ui\SearchableDropdown.tsx:42:7
  40 |   useEffect(() => {
  41 |     if (!isOpen) {
> 42 |       setSearch("");
     |       ^^^^^^^^^ Avoid calling setState() directly within an effect
  43 |       setActiveIndex(-1);
  44 |     }
  45 |   }, [isOpen]);  react-hooks/set-state-in-effect

C:\Users\itzza\CommDesk\src\context\SidebarContext.tsx
  32:17  warning  Fast refresh only works when a file only exports components. Use a new file to share constants or functions between components  react-refresh/only-export-components

C:\Users\itzza\CommDesk\src\context\ThemeContext.tsx
  40:17  warning  Fast refresh only works when a file only exports components. Use a new file to share constants or functions between components  react-refresh/only-export-components

C:\Users\itzza\CommDesk\src\features\Auth\v1\Pages\LoginPage.tsx
  44:5  warning  React Hook useCallback has a missing dependency: 'navigate'. Either include it or remove the dependency array  react-hooks/exhaustive-deps

C:\Users\itzza\CommDesk\src\features\Auth\v1\Pages\SignUpPage.tsx
  58:48  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any

C:\Users\itzza\CommDesk\src\features\Auth\v1\components\signup\OwnerStep.tsx
  396:51  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any
  404:60  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any

C:\Users\itzza\CommDesk\src\features\Auth\v1\hooks\useSignupForm.ts
  113:35  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any

C:\Users\itzza\CommDesk\src\features\Billing\v1\components\layout\QuickRecharge.tsx
  27:14  error  'e' is defined but never used  @typescript-eslint/no-unused-vars

C:\Users\itzza\CommDesk\src\features\Billing\v1\hooks\useWallet.ts
  9:3  error  'CreditTransaction' is defined but never used. Allowed unused vars must match /^_/u  @typescript-eslint/no-unused-vars

C:\Users\itzza\CommDesk\src\features\Dashboard\components\CalendarWidget.tsx
  19:5   error    Error: Calling setState synchronously within an effect can trigger cascading renders

Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.

Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).

C:\Users\itzza\CommDesk\src\features\Dashboard\components\CalendarWidget.tsx:19:5
  17 |
  18 |   useEffect(() => {
> 19 |     setSelectedDay(new Date().getDate());
     |     ^^^^^^^^^^^^^^ Avoid calling setState() directly within an effect
  20 |   }, [month, year]);
  21 |
  22 |   const today = new Date();  react-hooks/set-state-in-effect
  31:34  warning  Unexpected any. Specify a different type                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    @typescript-eslint/no-explicit-any

C:\Users\itzza\CommDesk\src\features\Events\v1\Components\EventSetting.tsx
  18:5  error  Error: Calling setState synchronously within an effect can trigger cascading renders

Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.

Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).

C:\Users\itzza\CommDesk\src\features\Events\v1\Components\EventSetting.tsx:18:5
  16 |
  17 |   React.useEffect(() => {
> 18 |     setToggled(isToggled || false);
     |     ^^^^^^^^^^ Avoid calling setState() directly within an effect
  19 |   }, [isToggled]);
  20 |
  21 |   React.useEffect(() => {  react-hooks/set-state-in-effect

C:\Users\itzza\CommDesk\src\features\Events\v1\Components\JudgeCard.tsx
  13:5  error  Error: Calling setState synchronously within an effect can trigger cascading renders

Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.

Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).

C:\Users\itzza\CommDesk\src\features\Events\v1\Components\JudgeCard.tsx:13:5
  11 |
  12 |   React.useEffect(() => {
> 13 |     setHasImageError(false);
     |     ^^^^^^^^^^^^^^^^ Avoid calling setState() directly within an effect
  14 |   }, [image]);
  15 |
  16 |   const initials = name  react-hooks/set-state-in-effect

C:\Users\itzza\CommDesk\src\features\Events\v1\Components\MentorCard.tsx
  13:5  error  Error: Calling setState synchronously within an effect can trigger cascading renders

Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.

Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).

C:\Users\itzza\CommDesk\src\features\Events\v1\Components\MentorCard.tsx:13:5
  11 |
  12 |   React.useEffect(() => {
> 13 |     setHasImageError(false);
     |     ^^^^^^^^^^^^^^^^ Avoid calling setState() directly within an effect
  14 |   }, [image]);
  15 |
  16 |   const initials = name  react-hooks/set-state-in-effect

C:\Users\itzza\CommDesk\src\features\Events\v1\Components\Partners_And_Sponsors_Card.tsx
  36:5  error  Error: Calling setState synchronously within an effect can trigger cascading renders

Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.

Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).

C:\Users\itzza\CommDesk\src\features\Events\v1\Components\Partners_And_Sponsors_Card.tsx:36:5
  34 |
  35 |   React.useEffect(() => {
> 36 |     setHasImageError(false);
     |     ^^^^^^^^^^^^^^^^ Avoid calling setState() directly within an effect
  37 |   }, [image]);
  38 |
  39 |   const initials = name  react-hooks/set-state-in-effect

C:\Users\itzza\CommDesk\src\features\Events\v1\Components\SpeakerCard.tsx
  13:5  error  Error: Calling setState synchronously within an effect can trigger cascading renders

Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
* Update external systems with the latest state from React.
* Subscribe for updates from some external system, calling setState in a callback function when external state changes.

Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect).

C:\Users\itzza\CommDesk\src\features\Events\v1\Components\SpeakerCard.tsx:13:5
  11 |
  12 |   React.useEffect(() => {
> 13 |     setHasImageError(false);
     |     ^^^^^^^^^^^^^^^^ Avoid calling setState() directly within an effect
  14 |   }, [image]);
  15 |
  16 |   const initials = name  react-hooks/set-state-in-effect

C:\Users\itzza\CommDesk\src\features\SideBar\v1\Section\SideBar.tsx
  10:3  error  'MdAccountBalanceWallet' is defined but never used. Allowed unused vars must match /^_/u  @typescript-eslint/no-unused-vars
  11:3  error  'MdBarChart' is defined but never used. Allowed unused vars must match /^_/u              @typescript-eslint/no-unused-vars

C:\Users\itzza\CommDesk\src\features\Tasks\v1\components\common\ToastNotification.tsx
  128:17  warning  Fast refresh only works when a file only exports components. Use a new file to share constants or functions between components  react-refresh/only-export-components

C:\Users\itzza\CommDesk\src\features\Webhooks\v1\components\form\WebhookForm.tsx
   37:17  warning  Unexpected any. Specify a different type                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      @typescript-eslint/no-explicit-any
   67:26  warning  Compilation Skipped: Use of incompatible library

This API returns functions which cannot be memoized without leading to stale UI. To prevent this, by default React Compiler will skip memoizing this component/hook. However, you may see issues if values from this API are passed to other components/hooks that are memoized.

C:\Users\itzza\CommDesk\src\features\Webhooks\v1\components\form\WebhookForm.tsx:67:26
  65 |   });
  66 |
> 67 |   const selectedEvents = watch("events");
     |                          ^^^^^ React Hook Form's `useForm()` API returns a `watch()` function which cannot be memoized safely.
  68 |
  69 |   const toggleEvent = (eventId: string) => {
  70 |     Telemetry.trackAction("webhook_form_toggle_event", { eventId });  react-hooks/incompatible-library
  129:28  warning  Unexpected any. Specify a different type                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      @typescript-eslint/no-explicit-any

C:\Users\itzza\CommDesk\src\features\Webhooks\v1\components\modals\PayloadModal.tsx
  8:12  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any

C:\Users\itzza\CommDesk\src\features\Webhooks\v1\components\table\LogsCardList.tsx
  15:81  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any

C:\Users\itzza\CommDesk\src\features\Webhooks\v1\components\table\LogsTable.tsx
  15:81  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any

C:\Users\itzza\CommDesk\src\features\Webhooks\v1\hooks\useWebhooks.test.tsx
  24:21  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any

C:\Users\itzza\CommDesk\src\shadcnComponet\ui\button.tsx
  62:18  warning  Fast refresh only works when a file only exports components. Use a new file to share constants or functions between components  react-refresh/only-export-components

C:\Users\itzza\CommDesk\src\theme\provider.tsx
  18:14  warning  Fast refresh only works when a file only exports components. Move your React context(s) to a separate file  react-refresh/only-export-components

C:\Users\itzza\CommDesk\src\types\markdown-to-jsx.d.ts
  29:31  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any

C:\Users\itzza\CommDesk\src\utils\telemetry.ts
   7:63  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any
  12:42  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any
  12:73  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any
  17:61  warning  Unexpected any. Specify a different type  @typescript-eslint/no-explicit-any

Γ£û 37 problems (12 errors, 25 warnings)