feat(eval): add Nuxt (Vue) PMS eval fixture - #55
Merged
Conversation
Faithful analog of the nextjs-pms eval fixture, built with Nuxt 3 (Vue). Same domain (spaces, reservations, derived guests), same operations, and the same reservations front-desk view that the integration agent extends. Part of ENG-2920. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
itelo
force-pushed
the
itelo/eng-2922-add-nuxt-vue-pms-eval-fixture
branch
from
August 24, 2026 18:10
47739e1 to
5bf4c82
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a Nuxt 3 (Vue) property-management app at
eval/fixtures/nuxt-pms/, a faithful cross-framework analog of the existingnextjs-pmsfixture. It manages spaces (bookable rooms, suites, cabins…), takes reservations against them, and lists the derived guests who have booked — the same domain, operations, and reservations front-desk view as the Next.js sample, so the two exercise the same integration.What's inside
better-sqlite3(no ORM); connection + schema inserver/utils/db.ts, created and seeded on first request.queries.ts,availability.ts,mutations.ts— plus sharedspace-kinds.ts, zodschemas.ts,types.ts, andformat.tsundershared/(imported via the#sharedalias by both server and pages).server/api/(book.post.ts,reservations/*,spaces/*,guests/*).pages/index.vue(booking form),pages/reservations.vue(front desk — the hook view),pages/spaces.vue(inventory),pages/guests.vue(directory), withlayouts/default.vuenav.[check_in, check_out)intervals (same-day turnover is not a conflict), cancelled releases the space, lexicographic ISO-date comparison, and a sharedassertSpaceBookableguard.Part of ENG-2920 (ENG-2922).
Testing
This fixture is fully excluded from the wizard's lint/tsc/tests (eslint
globalIgnores(['eval/fixtures/**']), tsc excludes fixtures,.prettierignorecoverseval/fixtures/, vitest never touches fixtures), so it has no impact on wizard CI. It is written to be coherent and idiomatic for an AI agent + LLM judge to read and extend.Security & Compliance
No security impact —
.env.exampleonly (no secrets), and the fixture is not built or executed by CI.🤖 Generated with Claude Code