chore(deps): update dependency @types/react to v18.3.18 (#546) #4
Annotations
13 warnings
Cypress
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Cypress
No files were found with the provided path: cypress/screenshots. No artifacts will be uploaded.
|
Build
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Build:
src/modules/analytics/context/DataProvider.tsx#L160
The 'descendantApps' conditional could make the dependencies of useMemo Hook (at line 250) change on every render. Move it inside the useMemo callback. Alternatively, wrap the initialization of 'descendantApps' in its own useMemo() Hook
|
Build:
src/modules/analytics/context/DataProvider.tsx#L167
Do not call the 'set' function 'setError' of 'useState' directly in 'useEffect'
|
Build:
src/modules/analytics/context/DataProvider.tsx#L173
Do not call the 'set' function 'setIsLoading' of 'useState' directly in 'useEffect'
|
Build:
src/modules/analytics/context/DataProvider.tsx#L175
Do not call the 'set' function 'setIsLoading' of 'useState' directly in 'useEffect'
|
Build:
src/modules/analytics/context/DataProvider.tsx#L177
Do not call the 'set' function 'setIsLoading' of 'useState' directly in 'useEffect'
|
Build:
src/modules/analytics/context/DataProvider.tsx#L192
Do not call the 'set' function 'setEnabledArray' of 'useState' directly in 'useEffect'
|
Build:
src/modules/analytics/context/DataProvider.tsx#L202
Do not call the 'set' function 'setActions' of 'useState' directly in 'useEffect'
|
Build:
src/modules/analytics/context/DataProvider.tsx#L203
Do not call the 'set' function 'setAllMembers' of 'useState' directly in 'useEffect'
|
Build:
src/modules/analytics/context/DataProvider.tsx#L204
Do not call the 'set' function 'setError' of 'useState' directly in 'useEffect'
|
Build:
src/modules/analytics/context/DataProvider.tsx#L214
Do not call the 'set' function 'setActions' of 'useState' directly in 'useEffect'
|