Migrate SolStatus onto Shared Project DNA #1
jonbeckmanvalidate.yml
on: pull_request
Repository validation
41s
Annotations
11 warnings
|
Repository validation
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
react(purity):
packages/app/src/components/latency-range-chart.tsx#L390
packages/app/src/components/latency-range-chart.tsx:390:36: Cannot call impure function during render
|
|
react(incompatible-library):
packages/app/src/components/data-table/data-table.tsx#L271
packages/app/src/components/data-table/data-table.tsx:271:17: Use of incompatible library
|
|
react(set-state-in-effect):
packages/app/src/hooks/use-mobile.ts#L14
packages/app/src/hooks/use-mobile.ts:14:5: Calling setState synchronously within an effect can trigger cascading renders
|
|
react(immutability):
packages/app/src/components/data-table/toolbar.tsx#L51
packages/app/src/components/data-table/toolbar.tsx:51:5: Cannot access variable while it is being initialized
|
|
eslint(no-unused-vars):
packages/app/src/components/endpoint-monitor-detail-header.tsx#L87
packages/app/src/components/endpoint-monitor-detail-header.tsx:87:12: Catch parameter '_e' is caught but never used.
|
|
react(set-state-in-effect):
packages/app/src/components/data-table/endpoint-monitor-detail-drawer.tsx#L92
packages/app/src/components/data-table/endpoint-monitor-detail-drawer.tsx:92:7: Calling setState synchronously within an effect can trigger cascading renders
|
|
react(set-state-in-effect):
packages/app/src/app/endpoint-monitors/[id]/page.tsx#L304
packages/app/src/app/endpoint-monitors/[id]/page.tsx:304:7: Calling setState synchronously within an effect can trigger cascading renders
|
|
react(set-state-in-effect):
packages/app/src/app/endpoint-monitors/[id]/page.tsx#L294
packages/app/src/app/endpoint-monitors/[id]/page.tsx:294:7: Calling setState synchronously within an effect can trigger cascading renders
|
|
react(refs):
packages/app/src/app/endpoint-monitors/[id]/page.tsx#L384
packages/app/src/app/endpoint-monitors/[id]/page.tsx:384:71: Cannot access refs during render
|
|
react(set-state-in-effect):
packages/app/src/components/nav-secondary.tsx#L32
packages/app/src/components/nav-secondary.tsx:32:5: Calling setState synchronously within an effect can trigger cascading renders
|