Weave Code
Suitable Laravel Package
laravolt/suitable
Laravolt Suitable is a Laravel package for adding approval workflows to Eloquent models. It provides configurable statuses, reviewer actions, and history tracking so records can be submitted, approved, or rejected with a clear audit trail.
[READ ONLY] Semantic UI Table Builder
Frequently asked questions about Suitable
- How do I install laravolt/suitable in a Laravel project?
- Install it with Composer using composer require laravolt/suitable. Laravel's package auto-discovery registers the service provider, so no manual registration is normally needed. Publish the package config and views with the vendor:publish command, then pin the constraint in composer.json to a reviewed version such as ^3.6.12. Commit the lock file so every environment resolves the same release.
- Which Laravel and PHP versions does laravolt/suitable support?
- Suitable is a Laravel-native package targeting PHP 8.x and modern Laravel releases, but the authoritative matrix is the require block in its composer.json. Check that block against the framework version you actually run, not just the newest one. Also verify the database versions in production, because JSON path behaviour can differ between MySQL, PostgreSQL and SQLite even when the package installs fine.
- What is a typical use case for laravolt/suitable?
- The package turns Eloquent query results into Semantic UI tables, so you define the columns, the underlying query, and any search or filter behaviour in PHP rather than hand-writing Blade markup. That suits admin panels, back-office listings, and reporting screens where stakeholders want sortable, filterable data grids. It fits projects already using Semantic UI, and it keeps table definitions close to the model layer instead of scattering view logic.
- Do I need Semantic UI CSS and JavaScript in my layout to use Suitable?
- Yes, in practice. Suitable emits Semantic UI table markup and classes, so the front end expects the Semantic UI stylesheet to be loaded for the table to render correctly. Add the Semantic UI assets to your layout, or compile the relevant parts through your asset pipeline. If your application already uses a different CSS framework, budget time for overriding styles or reconsider whether a Semantic UI-specific table builder is the right fit.
- Does Suitable support filtering on JSON columns with the -> operator?
- Release 3.6.12 added support for the -> operator when searching JSON columns, so a search layer can address nested document attributes such as meta->tier or payload->customer->region instead of only scalar columns. This is an additive change inside the existing query-building abstraction and introduces no new runtime dependency, queue, or storage layer. Confirm from the diff that the operator is translated per database driver rather than emitted as a raw SQL fragment, and test nested paths and array indices against your production database engine before exposing the feature to users.
- Is it safe to let users pass arbitrary column names or JSON paths into Suitable's search filters?
- Not without an allowlist. Any feature that lets a caller express a column path is a potential SQL injection surface if request parameters map straight onto column or path expressions. Constrain the addressable columns and JSON paths to a fixed, developer-defined set rather than trusting input, and reject malformed paths with a validation error instead of letting them reach the query builder. Treat this as the highest-severity review item whenever you extend the filter layer.
- Will JSON column filters slow down large tables?
- Possibly. JSON extraction is generally non-sargable, so a predicate such as meta->>'$.tier' = 'gold' will typically scan unless a functional index in PostgreSQL or a generated column plus index in MySQL backs it. The feature is functionally correct but can turn a filtering win into a latency regression at scale. Benchmark against realistic row counts and document the indexing strategy alongside the feature before enabling it in user-facing filters.
- How should I test a Suitable table integration before shipping it?
- Add feature tests that hit the endpoint with representative search and filter parameters, including JSON paths and malformed paths, and assert the returned rows rather than only the HTTP status. Run the suite against the same database engine and version used in production, since SQLite in-memory tests can mask driver differences in path syntax, type coercion and null semantics. Also assert that existing call sites still produce identical results after the upgrade, because additive features occasionally alter query shapes.
- What are the alternatives to laravolt/suitable?
- If you are not tied to Semantic UI, options include yajra/laravel-datatables for DataTables-style server-side grids, Livewire table components for reactive filtering and sorting, or a hand-rolled Blade table with a dedicated query filter class. Suitable's advantage is a small, Laravel-native abstraction that keeps table definitions in PHP next to your Eloquent models. Choose based on your CSS framework and how much client-side interactivity you need.
- Is laravolt/suitable actively maintained, and how risky is upgrading?
- Recent patch releases such as 3.6.12 indicate ongoing maintenance, so check the GitHub releases and changelog for cadence before committing. Upgrading is low risk because the change is additive and patch-versioned, meaning rollback is a constraint downgrade in composer.json with no schema or data implications. Still, read the diff to confirm the scope matches the release note, run the full suite on a branch, and add explicit tests for any new JSON filtering before enabling it in production.
Weaver
How can I help you explore Laravel packages today?