Skip to content

Latest commit

 

History

History
94 lines (80 loc) · 4.32 KB

File metadata and controls

94 lines (80 loc) · 4.32 KB

Changelog — dot

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.


0.8.1

Fixed

  • version14_ui never wired up @version14/ui/styles.css — the component library installed and typechecked fine, but nothing imported its precompiled CSS, so every scaffolded component rendered unstyled regardless of which styling engine (Tailwind, CSS Modules, Panda, or none) was picked. The import is now injected directly into the app's real entry point (src/main.tsx for react_app, src/app/layout.tsx for nextjs_base) by version14_ui itself, so it no longer depends on panda_css having run.
  • version14_ui never added @ark-ui/react as a dependency even though every @version14/ui component wraps an Ark UI primitive at runtime and in its type declarations — added explicitly, matching the ark_ui generator's own convention.
  • Bumped the @version14/ui pin to 0.8.0, which fixes the published package itself missing dist/styles.css from its npm tarball (present in 0.7.2 and earlier), and @pandacss/dev to ^1.11.4 to match its new peer range.
  • V14Example.tsx now actually renders Button imported from @version14/ui/button instead of static placeholder text, demonstrating the library's per-component subpath imports.
  • Added two tools/test-flow fixtures covering version14_ui on Next.js and on a non-Panda styling engine — the styles-import bug was invisible to the previous test coverage, which only ever combined version14_ui with panda-css on React+Vite.

0.6.0

Added

  • Decorator-based API validation and OpenAPI documentation flow (#91). When scaffolding an Express backend, dot now offers a @Controller/@Get/@Body decorator API with strongly-typed Zod schemas, request/response validation middleware, and an OpenAPI v3 spec served at /docs. Adapters ship for Clean Architecture, MVC, and Hexagonal projects, and a RouterAdapter interface keeps the system extensible to non-Express frameworks. See docs/user/decorators.md for the quickstart.
  • Classic JSDoc-driven Swagger fallback (express_swagger_jsdoc). When the decorator option is declined, dot still wires swagger-ui-express at /docs and ships @openapi JSDoc blocks on every generated handler (/health, /auth/*) so the spec is fully populated out of the box. The Swagger UI is therefore always available on a generated Express app — decorators only change how the spec is built.
  • auth_better_auth no longer emits an unused src/routes/auth.route.ts; the BetterAuth catch-all (toNodeHandler(auth)) is mounted directly in src/app.ts.
  • Case-level cache for tools/test-flow. A SHA-256 fingerprint over the fixture, every involved generator's source tree, the entire flows/ directory, pkg/dotapi/, and tools/test-flow/ itself is computed once scaffolding has resolved. On a hit, post-gen + test commands are skipped with a cache: HIT line in the report. Typical full warm runs go from ~7 min to ~4 s. Failed runs intentionally leave no cache entry. Disable with -no-cache or by removing .test-flow-cache/.
  • dotapi.Command.NoCache field. Commands are cacheable by default; generator authors opt out by setting NoCache: true on the relevant dotapi.Command{}. The case-level cache only short-circuits a case when no PostGen/Test command involved has NoCache: true. The Background dev-server probe in react_app (pnpm exec vite) ships with NoCache: true so a real boot is verified on every run. Cache schema bumped to v2 — existing .test-flow-cache/ entries are invalidated automatically.
  • tools/test-flow is now fail-fast by default — it stops at the first failing case so the failure surfaces immediately. Pass -keep-going to run every case (useful for triaging multiple unrelated failures or for CI runs that want a complete report). The summary line distinguishes total / failed / not run, e.g. ✗ 1/18 cases failed (10 not run).

Changed

Deprecated

Removed

Fixed

Security