CI

feat(RangeDateSelection): add new component #376

Sign in to view logs

Triggered via pull request September 3, 2024 08:02

ValeraS

synchronize #132

feat/range-date-selection

Status Success

Total duration 1m 3s

Artifacts –

ci.yml

on: pull_request

Annotations

10 warnings

Verify Files: src/components/DatePicker/hooks/useDatePickerProps.ts#L41

Unexpected any. Specify a different type

Verify Files: src/components/RangeDateSelection/__stories__/RangeDateSelection.stories.tsx#L161

'value' is already declared in the upper scope on line 81 column 16

Verify Files: src/components/RangeDateSelection/__stories__/RangeDateSelection.stories.tsx#L186

Forbidden non-null assertion

Verify Files: src/components/RangeDateSelection/__stories__/RangeDateSelection.stories.tsx#L187

Forbidden non-null assertion

Verify Files: src/components/RangeDateSelection/__stories__/RangeDateSelection.stories.tsx#L191

Forbidden non-null assertion

Verify Files: src/components/RangeDateSelection/__stories__/RangeDateSelection.stories.tsx#L192

Forbidden non-null assertion

Verify Files: src/components/RangeDateSelection/components/Ticks/UnavialableTicks.tsx#L42

The 'tickCoords' array makes the dependencies of useMemo Hook (at line 69) change on every render. To fix this, wrap the initialization of 'tickCoords' in its own useMemo() Hook

Verify Files: src/components/RangeDateSelection/components/Ticks/utils.ts#L135

'timeDiff' is already declared in the upper scope on line 112 column 11

Verify Files: src/hooks/useMove.ts#L143

'pageX' is already declared in the upper scope on line 133 column 24

Verify Files: src/hooks/useMove.ts#L143

'pageY' is already declared in the upper scope on line 133 column 31