Getting Started

Confirm your application is on Laravel 10 before adopting v0.1.11. This release adds Laravel 10 support and removes Laravel 6 and Laravel 8 support.
Install with composer require archtechx/gloss, then review the package README and published config/service provider first. Check the package’s documented entry points before wiring it into application code.
Start with one narrow use case: add a small set of gloss/translation data, retrieve it in a route or controller, and cover it with a feature test. This verifies Composer compatibility, config publishing, caching, and runtime behavior before rolling it out broadly.
If you are still on Laravel 6 or 8, stay on ^0.1.10 or upgrade Laravel first. Do not assume v0.1.11 will install or behave correctly on those versions.

Implementation Patterns

Wrap package calls behind a small application service or helper rather than scattering direct Gloss calls throughout controllers, views, and validation. This keeps the package boundary explicit and makes future upgrades or replacement easier.
Use Gloss as the central source for the gloss/translation domain you are modeling. Keep keys stable and grouped by feature or domain, and avoid generating keys dynamically at call sites.
Integrate retrieval into Laravel’s normal flow: controllers prepare data, views render it, form requests/validation use it where appropriate, and feature tests assert the resolved output for each supported locale.
For Laravel 10 projects, add v0.1.11 to your CI matrix and run the suite against the PHP/Laravel versions you actually deploy. Since L6 and L8 were dropped, remove those jobs from the package’s support matrix and update Composer constraints accordingly.
If the package stores data in the database or cache, include migrations/seed data and cache-clearing steps in deployment. Clear config, route, view, and translation caches after config or data changes.
Use the package’s config and service provider as extension points. Publish config only when you need to change defaults, and keep overrides in version control with comments explaining why they differ.

v0.1.11 is a compatibility release with a breaking support change: Laravel 6 and Laravel 8 are no longer supported. Check composer why archtechx/gloss and your lock file to ensure you are not silently pinned to an older release.
Laravel 10 requires a newer PHP baseline. Verify your local, CI, and production PHP versions before upgrading, especially if you maintain a package or multi-version application.
Composer may resolve an older Gloss version if your Laravel constraint is too loose. Explicitly require ^0.1.11 only in Laravel 10-compatible environments.
Cache issues are a common source of “it works locally but not in production” bugs. After changing config, translations, or gloss data, run the relevant php artisan optimize:clear or targeted cache-clear commands.
Do not rely on undocumented package APIs. Check the README/upgrade notes for v0.1.11 and confirm behavior with a small feature test before broad adoption.
Keep a thin adapter around Gloss if you expect to customize storage, locale resolution, or fallback behavior. This is also the best place to log misses or fallback usage during development.