Weave Code
Yoyo Laravel Package
clickfwd/yoyo
Yoyo is a Laravel package for quickly building CRUD interfaces and admin panels. It provides reusable components for tables, forms, and data management, helping you ship internal tools and dashboards with less boilerplate.
Yoyo is a full-stack PHP framework to create rich, dynamic interfaces using server-rendered HTML. You keep on writing PHP and let Yoyo make your creations come alive.
Frequently asked questions about Yoyo
- What is clickfwd/yoyo used for in Laravel?
- Yoyo is a Laravel package for quickly building CRUD interfaces and admin panels. It provides reusable components for tables, forms, and data management so internal tools and dashboards need less boilerplate. It fits Laravel apps that use Blade components or component-driven UI patterns.
- How do I install clickfwd/yoyo?
- Install it with Composer using composer require clickfwd/yoyo and follow the package setup for registering or using its components. The 0.15.1 release does not indicate any database or configuration migration. Check the repository README and composer.json for exact setup details and version constraints.
- Which Laravel and PHP versions does Yoyo support?
- The provided material does not list exact Laravel and PHP version constraints, so check the package composer.json and README before installing. Yoyo uses Illuminate Http Request, PHP reflection, and Laravel container resolution, so your Laravel and PHP versions must satisfy those dependencies. Pin a tested constraint in Composer rather than assuming support for every version.
- Does Yoyo work with Blade components and container-resolved arguments?
- Yes. Yoyo sits in Laravel's request-to-component binding layer and uses the service container and PHP reflection to hydrate component slots and public properties. It fits applications using Blade components, container-resolved arguments, or Livewire-style component rendering. Scalar slot values are largely unaffected by the 0.15.1 behavior change.
- How does Yoyo hydrate component slots and public properties from request data?
- Yoyo hydrates component slots and public properties from request data using the Laravel service container and PHP reflection, including JSON-decoded query values. In 0.15.1, request data no longer fills a slot declared to hold an object, while caller-supplied variables still can. The release also prevents JSON null and false from being re-hydrated as raw strings on every re-render.
- What changed in Yoyo 0.15.1?
- Yoyo 0.15.1 is a patch release that fixes request-to-component hydration behavior. It stops query-string data from displacing object slots, which could cause a 500 on an ordinary page load, and it addresses nullable object slots, union and intersection parameter types, and JSON scalar edge cases. It is a reliability and security-adjacent fix rather than a feature release.
- Should I upgrade to Yoyo 0.15.1 immediately?
- Yes, prioritize upgrading if you are on 0.15.0 or earlier because the 500-on-crafted-URL issue is externally triggerable. Update the Composer constraint to 0.15.1, run your full test suite, and audit code, tests, and deep links that relied on query parameters matching object slot names. Stage the update, exercise endpoints that accept query parameters, then deploy while monitoring for 500s and TypeErrors.
- Are object slots supposed to be caller-only, not filled from query strings?
- The 0.15.1 behavior indicates object slots are intended to be supplied by parent or caller variables rather than request data. Caller-supplied variables still fill object slots, but query-string data no longer does. Check the package documentation for explicit guidance and audit any nullable object slots or deep links that depended on the old behavior.
- How should I test Yoyo components after upgrading to 0.15.1?
- Add regression tests for object slots receiving query-string values, nullable object slots, union and intersection parameter signatures, and public properties hydrated from JSON null and false. Run component and integration tests plus the full suite after pinning 0.15.1 in staging. Also verify nested component model passing and pages that accept query parameters before production rollout.
- Is clickfwd/yoyo production-ready, and what about alternatives and maintenance?
- Yoyo is pre-1.0, so treat API stability as limited and pin versions while evaluating it for internal tools and dashboards. The material does not confirm a formal security policy, upgrade guide, or patch release cadence, so review release notes and monitor errors after upgrades. Compare it with your existing Blade or Livewire component approach and other Laravel admin panel packages based on version constraints, maintenance activity, and test coverage.
Weaver
How can I help you explore Laravel packages today?