omnisense/omnibridge dependents (6) 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
The storage glue of omnibase sites, framework-free: Doctrine reading the structure described outside of it (omnisense/omnibridge's Omnibridge\Schema), the naming strategy that turns their entities into their tables, the UTC date types, and an entity manager built with them, for any framework reading
-
PHP
omnibridge/symfony
The Symfony host of omnisense/omnibridge's contracts (urls, translations, access, sessions, tokens, environment) - adapters over Symfony's router, translator, security and kernel, their container wiring and OmnibridgeBundle - and the framework packages omnisense/omnibase no longer requires. A Symfon
-
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/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
-
PHP
omnibridge/eloquent
omnibase's entities on Eloquent's database layer, framework-free: illuminate/database (Laravel's connection, or Capsule outside Laravel) reading the tables omnisense/omnibridge's Omnibridge\Schema describes into the same plain PHP entities Doctrine maps - a data mapper: tables from the description,