omnisense/omnibridge dependents (7) Order by: downloads | none Show: all | require | require-dev
-
PHP
omnibridge/twig
The Twig side of omnibridge: the contract a page rendered with Twig asks of any framework (path, url, asset, trans - omnisense/omnibridge's Urls and Translations), the Twig extension that provides it where the framework does not, and helpers.
-
PHP
omnibridge/doctrine
omnibase's persistence on Doctrine, and the storage glue of omnibase sites, framework-free: Doctrine reading the structure described outside of it (omnisense/omnibridge's schema), the naming strategy, the UTC date types, an entity manager built with them; behind the core's contracts, the compiler of
-
PHP
omnibridge/symfony
The Symfony host of omnisense/omnibase: what is Symfony by nature in omnibase, declared under its Base\ names (Base\BaseBundle, the security glue, the form and field types, the controllers, the console commands, the kernel subscribers, the DI passes, the router), the adapters of omnisense/omnibridge
-
PHP
omnisense/omnibase
omnibase: entities, repositories, view models, contracts, forms and helpers for any PHP host - Base\ is what is provided, App\ the application that overrides it by the same path; under Symfony with omnibridge/symfony, under Laravel with omnibridge/laravel, persisted through omnibridge/doctrine or om
-
PHP
glitchr/typesense-bundle
Typesense for PHP the way Doctrine is for SQL: connections (DBAL), collections described by attributes or configuration, entities turned into documents and back, finders, queries and responses (ORM), and the indexing rule on Doctrine's events - framework-free; and its Symfony bundle.
-
PHP
omnibridge/eloquent
omnibase's persistence on Eloquent's database layer, framework-free: illuminate/database (Laravel's connection, or Capsule outside Laravel) reading the tables omnisense/omnibridge's schema describes into the same plain PHP entities any other persistence maps - a data mapper: tables from the descript
-
PHP
omnibridge/laravel
The Laravel host of omnisense/omnibase: its Foundation contracts (urls, translations, locales, access, parameters with the database settings laid over Laravel's config, clock, events...) answered by Laravel's services and seeded in Base\Contract\Runtime, the persistence through omnibridge/eloquent o