- What is juststeveking/api-toolbox used for in Laravel?
- It is a Laravel toolkit for building and documenting consistent, standards-compliant APIs. It provides helpers for responses, errors, and OpenAPI-ready resources so endpoint code stays clean and predictable. It also ships conventions and Laravel Boost guidance to help developers and coding agents apply the same API patterns.
- How do I install juststeveking/api-toolbox in a Laravel app?
- Install it through Composer, then run php artisan about --only=api_toolbox to confirm the installed version and feature state. For coding-agent assistance, run php artisan boost:install or php artisan boost:update. Enable non-experimental features first, then review any experimental features before production rollout.
- Which Laravel and PHP versions does api-toolbox support?
- The package is Laravel-native via Composer and Artisan, but this release summary does not list exact Laravel or PHP version constraints. Check the package composer.json and release notes before adoption. Compatibility checks should cover Laravel, PHP, and Laravel Boost availability for your environment.
- Is Laravel Boost required to use api-toolbox?
- No, Laravel Boost is not required for normal package use. It is used for coding-agent assistance and installs the package guideline and skill through boost:install or boost:update. The package remains usable as a Laravel-native Composer and Artisan dependency without Boost.
- Which api-toolbox features are marked Features::EXPERIMENTAL and what is the support policy?
- Features::EXPERIMENTAL explicitly identifies package features that may change in a minor release. The release exposes feature state and experimental status through the Artisan about integration. Treat experimental features as opt-in and review their status before enabling them in production.
- How can I check api-toolbox version and feature status in production?
- Run php artisan about --only=api_toolbox as a first diagnostic. It exposes the package version, feature state, experimental status, and signature key IDs and algorithms without leaking secrets or key paths. Support teams should include this command in runbooks and onboarding checks.
- How are signature key IDs and algorithms configured and rotated in api-toolbox?
- The about integration safely surfaces signature key IDs and algorithms, but not key material or key paths. Exact configuration and rotation steps should be taken from the package configuration and documentation. Keep key material and paths protected, and validate rotation by checking the about output.
- Is the apiguide.dev catalogue generated at build time, vendored, or fetched at runtime?
- The release summary notes that the solution depends on the generated apiguide.dev catalogue, but it does not state whether that catalogue is generated at build time, vendored, or fetched at runtime. Verify this before relying on it in your deployment model. The digest problem type URIs are unchanged, so no URI migration is required from this release.
- What compatibility guarantee does api-toolbox v0.x provide for minor releases?
- As a v0.x package, api-toolbox should be treated as early-stage, and minor releases may include changes. Features::EXPERIMENTAL explicitly marks features that can change in a minor release. Pin versions, review release notes, and keep experimental features behind explicit acceptance.
- How do I test that api-toolbox documentation and code examples stay in sync?
- The package includes a test asserting that documented classes, constants, middleware aliases, assertions, methods, and PHP snippets exist or parse. Include that documentation-integrity test in CI where applicable. Also assert expected php artisan about output for package version and feature status.