Weave Code
Axiom Laravel Package
gosuperscript/axiom
Axiom is a Laravel package that provides a set of well-crafted, reusable building blocks for common application concerns, with an expressive API, sensible defaults, and seamless integration into any Laravel project. It helps keep your code organized, consistent, and easy to maintain.
A PHP library for data transformation, type validation, and expression evaluation.
Frequently asked questions about Axiom
- What is gosuperscript/axiom and what does it do?
- gosuperscript/axiom is a Laravel Composer package that provides reusable building blocks for common application concerns, with an expressive API and sensible defaults. The technical assessment highlights structured query and filter parsing, including presence checks and equality operators. It is intended to keep Laravel code organized and consistent without requiring major architectural changes.
- How do I install gosuperscript/axiom in a Laravel app?
- Install it with Composer using the package name gosuperscript/axiom, then follow the repository README for any service provider or configuration steps. Because the provided README excerpt is empty, check the package repository for exact installation and publishing instructions. Pin the version you validate, especially while the package is pre-1.0.
- Which Laravel versions does gosuperscript/axiom support?
- The supplied context does not list specific Laravel version constraints, so check the package's composer.json and README before installing. Since the package is pre-1.0, verify compatibility against your exact Laravel and PHP versions in a branch. Pin a tested version rather than using a broad constraint.
- What changed in gosuperscript/axiom v0.6.10?
- v0.6.10 is a narrow patch release that resolves presence handling before equality overloads in query and filter parsing. It appears to be a correctness fix for operator precedence rather than a new integration surface. No data migration is implied by the release notes, but filter semantics should still be validated.
- Does the v0.6.10 presence-before-equality fix change existing query behavior?
- It can, because queries that rely on ambiguous presence and equality syntax may now resolve differently. The patch version implies backward compatibility, but precedence changes can affect API behavior without obvious type-level breakage. Add regression tests for combinations of presence and equality operators before rolling out.
- Is gosuperscript/axiom safe to use in production?
- The immediate release risk is low, but the package-level risk is medium because it is still pre-1.0. Use it as an application-layer dependency for request filtering or search, keep usage behind app-owned filter or service classes, and avoid exposing unbounded query grammar to public endpoints. Pin versions, review changelogs, and monitor filter parse failures and 4xx rates.
- How do I test query and filter parsing with gosuperscript/axiom?
- Add regression tests that cover presence checks, equality overloads, and mixed combinations of both, since the v0.6.10 fix changes precedence. Include application-level and API contract tests for the query strings your endpoints actually accept. Also test malformed query handling and confirm expected 4xx behavior.
- How should I upgrade gosuperscript/axiom from v0.6.9 to v0.6.10?
- Treat it as a patch bump: review the changelog and package tests, bump the dependency in a branch, and add targeted regression tests for presence and equality operator combinations. Run your application and API contract tests, then deploy to staging before production. No data migration is implied by the release notes.
- How is gosuperscript/axiom maintained and supported?
- Active patching is a positive signal, but gosuperscript/axiom is pre-1.0 and likely community-supported unless you have a commercial arrangement. Pin versions, review changelogs regularly, and be prepared to inspect the source or fork if critical filter semantics regress. Avoid broad version constraints until the package reaches a more stable release line.
- What are alternatives to gosuperscript/axiom for Laravel query filtering?
- The provided context does not name direct alternatives, so compare it with Laravel-native request filtering and other Composer query or filter packages. Evaluate operator support, documentation stability, Laravel version constraints, test coverage, and maintenance activity. Because Axiom is pre-1.0, weigh the cost of pinning and potentially forking.
Weaver
How can I help you explore Laravel packages today?