Skip to content

New Crowdin updates #4019

New Crowdin updates

New Crowdin updates #4019

Triggered via pull request January 15, 2026 00:18
Status Failure
Total duration 1m 2s
Artifacts

ci.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

1 error and 10 warnings
frontend
Process completed with exit code 1.
all: src/frontend/contexts/EarlyAccessContext.tsx#L1
In React 19, 'use' is preferred over 'useContext' because it is more flexible
all: src/frontend/contexts/DraftObservationContext.tsx#L51
In React 19, 'use' is preferred over 'useContext' because it is more flexible
all: src/frontend/contexts/DraftObservationContext.tsx#L44
In React 19, you can render '<Context>' as a provider instead of '<Context.Provider>'
all: src/frontend/contexts/CoordinateFormatStoreContext.ts#L64
In React 19, 'use' is preferred over 'useContext' because it is more flexible
all: src/frontend/contexts/CoordinateFormatStoreContext.ts#L1
In React 19, 'use' is preferred over 'useContext' because it is more flexible
all: src/frontend/contexts/AuthContext.tsx#L126
In React 19, you can render '<Context>' as a provider instead of '<Context.Provider>'
all: src/frontend/contexts/AuthContext.tsx#L22
In React 19, 'use' is preferred over 'useContext' because it is more flexible
all: src/frontend/contexts/ActiveProjectIdStoreContext.tsx#L107
In React 19, 'use' is preferred over 'useContext' because it is more flexible
all: src/frontend/contexts/ActiveProjectIdStoreContext.tsx#L1
In React 19, 'use' is preferred over 'useContext' because it is more flexible
all: src/frontend/contexts/ActiveProjectContext.tsx#L28
In React 19, 'use' is preferred over 'useContext' because it is more flexible