- What is 3neti/instruction used for in a Laravel app?
- 3neti/instruction lets you define reusable, structured instruction workflows so step-by-step logic lives in dedicated classes instead of bloated controllers or services. It provides a clean API for declaring instructions, composing instruction sets, and keeping behavior readable and maintainable. It is lightweight and integrates with familiar Laravel conventions, making it suitable for any PHP or Laravel application that needs repeatable workflow logic.
- How do I install 3neti/instruction with Composer?
- Install it with Composer using composer require 3neti/instruction and let Laravel package discovery register the service provider. The package is described as lightweight with minimal configuration, so most setups should only need to publish configuration if the README instructs you to. After installation, define your first instruction class and wire it into a controller, service, or command.
- Which Laravel and PHP versions does 3neti/instruction support?
- The package is built for modern Laravel applications and follows native Laravel conventions, but the exact supported Laravel and PHP matrix should be confirmed in the repository composer.json and README. Because the technical assessment notes dependencies such as Bavix Laravel Wallet and Brick Money on the wallet and pricing side, those packages can constrain the effective version matrix. Check compatibility before upgrading a production application.
- Does 3neti/instruction require Bavix Laravel Wallet?
- Wallet-backed instruction features rely on Bavix Laravel Wallet, which brings its own schema, migrations, and transactional semantics. If your application already uses Bavix, this is a natural fit; if you use a different ledger, Cashier, or custom accounting model, those wallet-enabled instruction items may need an adapter layer or may not be useful to you. Teams not using the wallet features should verify which parts of the package remain relevant to their workflow.
- How does 3neti/instruction handle prices and money?
- The package uses Brick Money with integer minor units, avoiding floating-point arithmetic for money. It exposes dual fields such as price and price_minor or total_amount and total_amount_minor, where the minor-unit field should be treated as authoritative for accounting reconciliation and the decimal field as presentational. Floats are rejected, so code paths must pass a string like 5.00 or an integer like 500 at write boundaries.
- Can I migrate existing float-based price data to 3neti/instruction?
- The 0.2.x release introduces a breaking change to price typing, and migrating existing float columns to minor-unit integers requires a backfill with per-currency rounding decisions. You should not assume a migration path exists; confirm whether the package documents and tests one before converting production data. Errors in this conversion are financial errors, so plan and verify the backfill carefully.
- Is 3neti/instruction production-ready?
- The package is at a pre-1.0 version, so SemVer permits breaking changes and the broad money-related change in 0.2.x carries integration cost. It is highest-fit for greenfield or pre-production Laravel applications and lowest-fit for systems already persisting float prices or using a different ledger. Before production use, verify test coverage for wallet flows, rounding edge cases, concurrency, and transactional boundaries.
- How do I test instruction workflows built with 3neti/instruction?
- The package is designed to be easy to test, reuse, and maintain because instructions are encapsulated and composable. Write unit tests around individual instruction classes and integration tests around composed sets, including wallet mutations and pricing calculations where applicable. The release claims full coverage across wallet flows, pricing, API responses, and persistence, but you should verify that claim against your own edge cases rather than assume it.
- What are alternatives to 3neti/instruction for Laravel workflows?
- Common alternatives are Laravel pipelines, action or service classes, jobs, and custom workflow engines, depending on whether you need simple step composition or durable orchestration. If your main concern is ledger-backed financial instructions, Bavix Laravel Wallet or a custom double-entry system may be more central than this package. 3neti/instruction is best viewed as a lightweight way to organize reusable instruction logic, not as a full financial ledger by itself.
- How is 3neti/instruction maintained and what is the roadmap to 1.0?
- The package is currently in the 0.2.x line, and the technical assessment explicitly asks about the roadmap to 1.0 and whether further breaking changes to the money contract will be batched. Maintenance health should be checked through the repository release history, issue activity, and test suite. Also ask whether price history is append-only or pruned, and what the supported dependency matrix is for Bavix Wallet, Brick Money, Laravel, and PHP.