Xrowregexpline Bundle Laravel Package

Product Decisions This Supports

• Legacy modernization triage: Use this package only as a signal that an existing eZ Publish 5 site depends on the custom xrow Regexpline datatype. It supports decisions to inventory, contain, and migrate those legacy content-validation fields rather than extend them.
• Roadmap: Keep it off the roadmap for new Laravel/PHP products. If a legacy surface still depends on it, schedule migration to native Laravel validation, a maintained validation library, or a simpler content model.
• Build vs buy: Do not build new functionality around it. Treat it as an unsupported compatibility artifact; if changes are needed, prefer a small internal fork/patch pinned to the legacy environment over a broader adoption.
• Use cases: Maintaining old eZ5 content forms, preserving Regexpline validation during migration, extracting/validating legacy content, and assessing data-model risk before replatforming.
• Risk decision: Zero stars, zero dependents, and a last release in 2016 indicate abandoned, low-community-support code. Product should fund replacement or containment, not new dependency.

When to Consider This Package

Consider it only when all of the following are true:

• You maintain a legacy eZ Publish 5 application.
• That application uses xrow custom datatypes and specifically Regexpline fields.
• You need a minimal compatibility fix during maintenance or migration.
• You can pin PHP/framework versions and accept unsupported, unmaintained code.
• The alternative—rewriting the field logic or migrating content—is not yet feasible.

Look elsewhere when:

• You are building or modernizing a Laravel application.
• You need maintained security, PHP-version compatibility, or vendor support.
• You need generic regex validation; Laravel’s validator or a maintained package is a better fit.
• You have no existing eZ5/Regexpline dependency. In that case, do not adopt this package.
• You expect community ecosystem support; there is no evidence of it here.

How to Pitch It (Stakeholders)

For executives: This is not a strategic package. It is abandoned legacy eZ5 compatibility code with no visible adoption. Do not invest in expanding it; fund containment and migration away from any dependency.

For engineering: Treat it as a legacy shim only. Isolate it, document the exact eZ5/Regexpline dependency, pin versions, and plan replacement with native Laravel validation or a maintained PHP validation approach. Do not introduce it into new services or shared libraries.

For product: The decision is not “adopt this package”; it is “identify affected legacy content, avoid new dependency, and prioritize migration.” Any feature work touching Regexpline should be scoped as legacy remediation, not new product capability.