Skip to content

fix: resolve CI lint errors#852

Open
AntonioVentilii wants to merge 1 commit into
mainfrom
fix/ci-lint-errors
Open

fix: resolve CI lint errors#852
AntonioVentilii wants to merge 1 commit into
mainfrom
fix/ci-lint-errors

Conversation

@AntonioVentilii

@AntonioVentilii AntonioVentilii commented Jun 18, 2026

Copy link
Copy Markdown
Collaborator

Fixes the failing CI linters.

  • svelte/no-navigation-without-resolve: wrap the internal /browser link in resolve() in resources/+page.svelte.
  • vitest/no-conditional-expect: remove expect calls nested in conditionals/&& guards in ChipGroup, Dropdown, ProgressBar and Input specs (narrowing with assertNonNullish where needed).

eslint + prettier clean; 64 affected tests pass.

- resources page: wrap internal href with resolve() (svelte/no-navigation-without-resolve)
- ChipGroup/Dropdown/ProgressBar/Input specs: remove conditional expect
  calls by narrowing with assertNonNullish and asserting unconditionally
  (vitest/no-conditional-expect)
@AntonioVentilii AntonioVentilii requested review from a team as code owners June 18, 2026 06:28
@zeropath-ai

zeropath-ai Bot commented Jun 18, 2026

Copy link
Copy Markdown

No security or compliance issues detected. Reviewed everything up to 12029ea.

Security Overview
Detected Code Changes
Change Type Relevant files
Refactor ► src/routes/(page)/resources/+page.svelte
    Use resolve for internal links
► src/tests/lib/components/ChipGroup.spec.ts
    Simplify class checking logic
► src/tests/lib/components/Dropdown.spec.ts
    Use assertNonNullish for DOM element checks
► src/tests/lib/components/Input.svelte.spec.ts
    Use assertNonNullish for DOM element checks
► src/tests/lib/components/ProgressBar.spec.ts
    Use assertNonNullish for DOM element checks
Enhancement ► src/tests/lib/components/Dropdown.spec.ts
    Import assertNonNullish for better type safety

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant