Download the PHP package middag-io/moodle without Composer
On this page you can find all versions of the php package middag-io/moodle. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download middag-io/moodle
More information about middag-io/moodle
Files in middag-io/moodle
Package moodle
Short Description MIDDAG Moodle adapter — platform bindings, ACL layer, and Moodle-specific implementations for middag-framework
License Apache-2.0
Homepage https://github.com/middag-io/middag-php-moodle
Informations about the package moodle
middag-io/moodle
MIDDAG Moodle adapter — platform bindings, ACL layer, and Moodle-specific
implementations of the middag-io/framework
contracts.
License: Apache-2.0.
What this package is
middag-io/moodle is the Moodle host adapter for the MIDDAG framework. It
provides the Moodle-side implementations of the framework's adapter contracts —
bootstrap, config resolution, signal dispatch, command bus, user context — plus
Moodle API wrappers (Support/), entities, DTOs, settings types, and HTTP /
Inertia infrastructure.
It binds the framework to a Moodle site. A Moodle plugin provides the
composition root that wires it in; any local_* or mod_* plugin can play that
role.
What it does not include
- No product features, business rules, or governed domain capabilities.
- No dependency on any non-OSS MIDDAG package — the adapter builds only on the
OSS framework and the host platform. Importing any non-OSS MIDDAG namespace or
package is forbidden and enforced by the adapter isolation guard test
(
tests/AdapterPluginIsolationTest.php, part ofcomposer test). - No bundled Moodle plugin. You wire the adapter into your own plugin.
Requirements
- PHP
^8.2(tested on 8.2, 8.3, 8.4) ext-json- A Moodle site (the adapter targets Moodle's runtime APIs)
Installation
This pulls middag-io/framework and middag-io/ui automatically.
The
middag-io/*packages are published on Packagist, so they resolve from the default Composer registry with no extra configuration. No manualrepositoriesentry is required.
Development
Run the quality gates and the test suite:
Git hooks are configured automatically via post-install-cmd. The commit-msg
hook enforces Conventional Commits.
Working against a sibling framework checkout
This package declares no repositories entries: middag-io/framework (and
every other dependency) resolves from the default Composer registry. To edit
the framework and the adapter side by side, declare the path repository in the
consuming (root) project's composer.json — Composer only reads the root
package's repositories; entries inside a dependency would be ignored anyway:
This is a development-only convenience in the consumer. Published releases of this package always resolve through the normal Composer registry.
composer.lock is gitignored
Like a typical library, this repo does not commit composer.lock; consumers pin
versions in their own application. Because local development may resolve the
framework through a consumer-declared path repository, a local
composer.lock can show path or dev references. That is expected local
development state and not a defect in the released package.
See CONTRIBUTING.md for the full contributor setup,
including the dependency-resolution notes.
Commit format
Releases
Releases are managed by release-please.
Conventional commits merged to main open a Release PR automatically.
License
Licensed under the NOTICE for
attribution.
All versions of moodle with dependencies
ext-json Version *
firebase/php-jwt Version ^7.0
middag-io/framework Version ^1.7
middag-io/ui Version ^1.3
nyholm/psr7 Version ^1.8
psr/container Version ^2.0
psr/log Version ^3.0
psr/simple-cache Version ^3.0
symfony/dependency-injection Version ^7.0
symfony/event-dispatcher-contracts Version ^3.0
symfony/http-client Version ^7.0
symfony/http-foundation Version ^7.0
symfony/routing Version ^7.0