Weave Code
Symfony Extension Laravel Package
short-edition/symfony-extension
A Symfony bundle that integrates Short Edition's short-story publishing platform into PHP applications, offering ready-made services, configuration, and API client support for fetching and displaying short fiction content.
Integrates Behat with Symfony.
Frequently asked questions about Symfony Extension
- What is short-edition/symfony-extension and what does it do?
- It is presented as a lightweight Symfony bundle that integrates Short Édition content and services, registering services, exposing configuration, and adding Twig and HTTP client support. The technical review, however, identifies it as a Behat extension for Symfony full-stack applications, likely a fork of friends-of-behat/symfony-extension rather than an independent Short Édition client. Treat the package description with caution and verify the actual code before adopting it.
- Is short-edition/symfony-extension compatible with Laravel?
- No. It is built around the Symfony kernel and service container, and the review states it cannot be dropped into Laravel without a kernel shim or replacement extension. For Laravel applications, use Pest or PHPUnit with Laravel's HTTP testing helpers instead.
- How do I install short-edition/symfony-extension with Composer?
- You would normally require it with composer require short-edition/symfony-extension and enable the bundle in a Symfony application, following Flex-style bundle registration where supported. Before installing, run a timeboxed Composer resolution spike against your actual PHP, Symfony, and Behat versions because modern PHP 8.x and Symfony 6/7 compatibility is unproven. Do not install it in a Laravel project.
- Which Symfony, PHP, and Behat versions does short-edition/symfony-extension support?
- The provided context does not list exact version constraints, and the review warns of probable pinning to older Behat, Symfony, and PHP versions. Composer resolution against modern PHP 8.x and Symfony 6 or 7 is unproven and likely to conflict. Check the composer.json and run a resolution spike before relying on any version claim.
- How do I configure short-edition/symfony-extension in a Symfony app?
- The bundle is described as exposing clean configuration through a dedicated DI extension, with sample configuration present in its sources. The review notes that leftover sample config still references the FriendsOfBehat\SymfonyExtension namespace, which supports the view that it is a fork. Validate the configuration keys against the actual package code rather than assuming the README is complete.
- Does short-edition/symfony-extension provide Twig helpers for short stories?
- The overview claims Twig helpers for rendering short-story content, but the technical review does not confirm that this is the package's real capability. Because the package appears to be a Behat/Symfony extension fork, verify whether any Twig helpers exist in the source before designing templates around them. If they do exist, treat them as unmaintained integration code.
- Does it include an HTTP client for the Short Édition API?
- The description mentions PSR-compatible HTTP client integration, but the technical assessment provides no evidence of a maintained Short Édition API client. The package is more credibly a Behat extension for booting a Symfony kernel and exposing the container to contexts. Do not assume API coverage without inspecting the source.
- Can I use short-edition/symfony-extension for Behat testing in Symfony?
- The review says that is what the package actually is: a Behat extension that boots a Symfony kernel, wires the container, and injects services into contexts. However, it duplicates the maintained friends-of-behat/symfony-extension and is an archived, zero-star fork. For Symfony test suites, use the maintained upstream integration instead.
- Is short-edition/symfony-extension maintained and safe for production?
- No, the review rates technical risk as high: the repository is archived, has zero stars and dependents, no release cadence, and no CVE response path. It is test glue code, not a production runtime dependency, but retaining a fork still creates internal ownership and security exposure. Gate any use behind a short spike and a named owner.
- What should I use instead of short-edition/symfony-extension?
- For Symfony, migrate to the maintained friends-of-behat/symfony-extension; the config namespace already matches upstream, so migration is closer to a dependency swap than a rewrite. For Laravel, standardize on Pest or PHPUnit with Laravel HTTP testing helpers, and only build a small internal Behat extension if feature-file readability justifies it. Treat this package as a reference implementation, not a library to adopt.
Weaver
How can I help you explore Laravel packages today?