Skip to content

chore: update prod from main#1341

Open
github-actions[bot] wants to merge 4 commits into
prodfrom
main
Open

chore: update prod from main#1341
github-actions[bot] wants to merge 4 commits into
prodfrom
main

Conversation

@github-actions

Copy link
Copy Markdown

This pull request updates the prod branch with the latest changes from the main branch.

⚠️ Do not squash-merge! ⚠️

Make sure to merge this creating a merge commit.

## Summary

- Adds `useWasapPageData.spec.ts` with 17 tests covering all 5 fetch
modes: manual, resistance, variant (computed + predefined signatures),
untracked (custom + predefined exclude sets), and covSpectrumCollection
— including enabled, disabled, and error cases
- Exports `fetchWasapPageData` for direct testing (avoids React Query
`renderHook` setup)
- Adds `BackendRouteMocker.mockGetCollection` to `routeMocker.ts`
- Converts `SignatureType`, `WasapAnalysisMode`, and `ExcludeSetName`
from bare string unions to the const-object pattern (matching
`VARIANT_TIME_FRAME`), and adds `SEQUENCE_TYPE` for the external
`SequenceType`

## Test plan

- [x] `npx vitest run
src/components/views/wasap/useWasapPageData.spec.ts` — all 17 tests pass
- [x] `npx tsc --noEmit` — no errors

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
@vercel

vercel Bot commented Jul 15, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
dashboards Ready Ready Preview, Comment Jul 15, 2026 9:21am

Request Review

- astro: ^5.18.1 → ^6.4.8
- @astrojs/node: ^9.5.3 → ^10.1.4 (v10 requires astro ^6.3.0)
- @astrojs/react: ^4.4.2 → ^5.0.7

No code changes needed: the project has no content collections, no
ViewTransitions, no legacy experimental flags, and all Astro imports use
stable APIs that are unchanged in v6.


Upgrade guide: https://docs.astro.build/en/guides/upgrade-to/v6/

Co-authored-by: Felix Hennig <felix-agent@felixhennig.com>
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
)

## Summary

- Wraps `authClient.signIn.social()` in a `useMutation` hook, replacing
the raw `.catch()` pattern
- Moves error handling to the `onError` callback, consistent with how
other async operations are handled in the codebase
- Wraps the component with `withQueryProvider` so it has access to the
query client

Closes #1209

🤖 Generated with [Claude Code](https://claude.ai/claude-code)

Co-authored-by: Felix Hennig <felix-agent@felixhennig.com>
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
…1318)

resolves #1217

### Summary

Two related changes:

**1. `AdvancedQueryFilter.onInput` now reports validity.** Previously it
only fired on valid input, giving callers no way to know when the
current value is invalid (e.g. to disable a form submit button). The
hook now always fires after validation completes, with an `isValid`
boolean as the second argument.

New signature:
```ts
onInput?: (newValue: string | undefined, isValid: boolean) => void
```

Behavior by state:
- Cleared → `onInput(undefined, true)`
- Valid → `onInput(query, true)` *(unchanged)*
- Parse error / disallowed field / network error → `onInput(query,
false)` *(previously not called)*

Existing callers (`BaselineSelector`, `VariantSelector`) updated to only
propagate the value to state when `isValid` is `true`, preserving prior
behavior.

**2. Collection form: disable submit while an advanced query is
invalid.** In the collection create/edit form, a variant defined via
advanced query now blocks submitting while its query is invalid. An
empty advanced query is also treated as invalid (it is not a usable
variant definition). `VariantEditor` reports each variant's validity up
to `CollectionForm`, which disables the submit button while any variant
is invalid.

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: Fabian Engelniederhammer <fabian.engelniederhammer@tngtech.com>
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.

2 participants