Changelog

Latest release changes

GoLazy v0.1.10 focuses on application-flow helpers: form decoding in controllers, route helper query parameters, nested REST resources, detailed development errors, and the new lazytest package for full handler tests.

Framework

• golazy.dev/lazytest provides complete application-handler tests, named route requests, body/header assertions, JSON decoding, and cookie-aware clients. Read Release Verification and Controller Tests.
• Controllers can call c.Decode(&form) to parse request forms through lazyschema and return bad-request errors for invalid submissions. Read Forms.
• PathFor accepts trailing lazycontroller.URLParams, and MustPathFor panics for route names and arguments that are application invariants. Read Controller Routes.
• REST resources can nest child resources under parent member paths. Read REST Resources.
• Applications can force detailed error responses with lazyapp.Config.ForceDetailErrors, while lazy development builds show detail by default. Read Redirects, Metadata, And Errors.

Runtime behavior

• Automatic controller rendering keeps HTML as the default render format even when Turbo Stream is accepted, while explicit Render calls still honor the selected request format. Read Formats And MIME.
• Default session names derived from module-path app names use the module basename, so generated applications get shorter cookie names.
• Unexpected controller errors are logged to stderr before the framework sends the configured error response.

CLI and generated apps

• lazy hot reload ignores no-op lockfile timestamp rewrites from package managers while still rebuilding on real package metadata changes. Read lazy Dev Loop Integration.
• lazy new selects the matching sample application template with lazytest-based application tests, .secrets development configuration, SECURE_COOKIE_KEY environment wiring, and Docker packaging. Read Configuration and Deployment.

Read the Upgrade Guide before moving an existing application forward.