flyokai/application-core

Sync framework core for Flyokai: bootstrap, dependency injection, setup steps, console base, schema/DDL columns and repositories. No async runtime (AMPHP event loop / Revolt), so it can be hosted inside synchronous PHP frameworks (e.g. Shopware) via flyokai/marketplace-embedded.

Maintainers

Package info

github.com/flyokai/application-core

pkg:composer/flyokai/application-core

Statistics

Installs: 0

Dependents: 0

Suggesters: 0

Stars: 0

Open Issues: 0

Security

Advisories: 0

Aikido package health analysis

v1.1.0 2026-06-04 17:11 UTC

Requires

MIT bd65cc595a80c317935b2dd93f216b73bff73e20

This package is auto-updated.

Last update: 2026-06-04 18:21:28 UTC

README

Sync slice of flyokai/application. No AMPHP, no Revolt, no event loop.

Holds the classes that pure-sync hosts (e.g. Shopware running marketplace locally via flyokai/marketplace-embedded) need to consume from flyokai/marketplace-core without pulling Amp transitively.

Current contents

  • Base\AbstractRepository — abstract base for entity repositories. Uses #[ServiceParameter] as metadata only; the attribute is never instantiated in sync hosts.
  • Base\ExtensionRepositoryTrait — DTO-extension repository trait.
  • DB\ConnectionPool — interface only. The Amp implementation lives in flyokai/application; sync hosts provide their own via flyokai/marketplace-embedded\SyncConnectionPool.
  • Exception\EntityNotFoundException
  • Http\Controller\ProtectedHandler — marker interface (was historically named for HTTP handlers but is used as a generic "requires auth" marker on any request handler).

BC bridge

The previous namespaces (Flyokai\Application\…) are kept alive as class_alias stubs inside flyokai/application, so existing consumers continue to work without an import sweep. New code should use the Flyokai\ApplicationCore\… names.