- What is marshmallow/laravel-linear and what does it do?
- marshmallow/laravel-linear is a Laravel integration for Linear's issue-tracking API. It provides a configured GraphQL client, a facade, and fluent helpers so Laravel applications can query and manage Linear issues, projects, teams, and workflows. It is best treated as an API integration layer, with your application owning jobs, events, retries, and business logic.
- How do I install marshmallow/laravel-linear with Composer?
- Install the package with Composer using composer require marshmallow/laravel-linear. Laravel package auto-discovery typically registers the service provider and facade, but confirm the README for any publish or configuration steps. After installation, set your Linear API credentials in the package configuration and clear cached config if needed.
- How do I configure laravel-linear to connect to Linear?
- Publish the package configuration if the README instructs you to, then add your Linear API token and any required workspace or team settings. Keep the token in your environment file rather than committing it. Run php artisan config:clear after changes and verify the GraphQL client can reach Linear with a simple query.
- Which Laravel and PHP versions does laravel-linear support?
- The v1.4.1 release notes do not indicate a change to Laravel or PHP version constraints. Check the package composer.json for the authoritative support matrix before adoption. If your application uses an older Laravel or PHP version, confirm compatibility in a staging branch first.
- What Linear resources can I manage with laravel-linear?
- The package exposes a configured GraphQL client, facade, and fluent helpers for Linear's issue-tracking API. It is intended for querying and managing issues, projects, teams, and workflows from your Laravel app. You still need application-level jobs, events, and business logic around those calls.
- What changed in laravel-linear v1.4.1?
- v1.4.1 is a patch release whose meaningful runtime change is that a message value can now be null. The webpack bump is development and build tooling and should not affect production runtime. Review PR #18 for the exact class, property, or return type that became nullable.
- Is the nullable message change in v1.4.1 a breaking change?
- At the package level it is a patch release, but it can behave like a breaking change in strict consumers that type-hint string or pass message to non-nullable parameters. It is safe if your code handles null or supplies a fallback value. Run static analysis and null-case tests before upgrading.
- How should I handle null message values from Linear in my Laravel app?
- Add null guards anywhere you consume the message value, including serialization, notifications, Blade templates, and downstream API calls. Define fallback copy such as No message provided when displaying it to users. Cover those paths with tests and update PHPStan or Psalm baselines if they flag new nullable paths.
- What are the production risks of using laravel-linear?
- The package is an API client, so production risk is tied to Linear API rate limits, token expiry, and retry or backoff behavior in your application. The nullable message contract can surface as TypeErrors or blank UI if null propagates into strict handlers or templates. Treat retries, rate limiting, and business logic as application-owned concerns and monitor logs for null-related exceptions.
- How do I test laravel-linear and null-message handling before upgrading?
- Pin v1.4.0 first to capture current behavior, then inspect the v1.4.1 diff and PR #18 for the nullable signature. Update in staging and add tests for null message rendering, serialization, notifications, and downstream calls. Run your full test suite and static analysis, then roll out to production and monitor for empty-message regressions.