Bitrix Taxidermist Laravel Package

Product Decisions This Supports

• Developer tooling and migration roadmap: Release 0.2.0 expands coverage of Bitrix main and sale module classes and adds Cache::$hasOutput, Cache::output(), and Cache::noOutput(). This is most consistent with a stubs / IDE / static-analysis support package rather than a runtime Laravel integration. It supports decisions about how much to invest in tooling for legacy Bitrix code while migrating to Laravel.
• Build vs. buy: If your team maintains hand-written stubs or ignores Bitrix classes in static analysis, this package is a candidate to replace that internal maintenance. The growing class surface (especially sale) reduces the amount of custom stub work needed.
• Migration scoping: Coverage of main and sale helps PMs define which legacy modules can be safely analyzed, refactored, or wrapped first. sale is typically the highest-risk/highest-value module, so its inclusion is a meaningful signal for prioritization.
• Quality and risk management: A 0.2.x release implies pre-1.0 API instability. Plan for version pinning and a lightweight evaluation gate (static-analysis baseline, license review, maintainer activity) before broad adoption.
• Not a runtime capability decision: Do not treat the added Cache::output() / noOutput() methods as production caching features unless you confirm this package ships runtime behavior. If it is stubs-only, it improves type safety and IDE support but does not change application performance.

When to Consider This Package

• You maintain or migrate legacy Bitrix code alongside Laravel/PHP, and your IDE or static analysis (PHPStan/Psalm/PhpStorm) produces false positives or missing completions for Bitrix\Main and Bitrix\Sale classes.
• You want accurate type information for cache output control ($hasOutput, output(), noOutput()) without writing and maintaining your own stubs.
• You are willing to accept pre-1.0 churn and pin versions, with a periodic review of new class coverage per release.
• You need a low-risk, dev-only dependency that improves onboarding and code review for engineers unfamiliar with Bitrix internals.
• Look elsewhere if you need a true runtime bridge (DI container integration, routing, auth, ORM, events) between Laravel and Bitrix, a supported long-term vendor SLA, or full-module coverage beyond main and sale. Also look elsewhere if you have fully exited Bitrix or prohibit generated/stub code in your repository.

How to Pitch It (Stakeholders)

For executives: This is a low-cost developer-productivity dependency that reduces friction in maintaining and migrating legacy Bitrix code. It carries no runtime risk if adopted as a dev-only tool, and version 0.2.0 broadens coverage of the high-value sale module and cache output APIs. Recommend a time-boxed pilot with pinned versions before wider rollout.

For engineering: Release 0.2.0 adds Cache::$hasOutput, Cache::output(), and Cache::noOutput(), plus many new main and sale classes — improving IDE completion, static-analysis accuracy, and type safety for legacy code paths. Because it is pre-1.0, pin the version, validate against your PHPStan/Psalm baseline, and confirm whether the package is stubs-only or provides runtime behavior before relying on it in production flows.