Download the PHP package maatify/shared-common without Composer
On this page you can find all versions of the php package maatify/shared-common. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package shared-common
Maatify SharedCommon
Overview
The Maatify\SharedCommon module contains foundational contracts and abstractions that are intended to be shared across all Maatify modules (such as AdminKernel, Verification, etc.). Its primary goal is to provide unified interfaces for common cross-cutting concerns like time management, security contexts, permission mapping definitions, and telemetry, enabling consistent behavior and testing across the entire system.
Purpose
By depending on SharedCommon rather than framework-specific implementations or raw PHP functions (like time() or date()), other modules can remain truly framework-agnostic. This module defines the "how we communicate" contracts for basic system realities.
Module Structure
Quick Usage
To quickly integrate the default implementations of this module into your dependency injection container:
Permission Mapping Contracts
SharedCommon provides framework-neutral permission mapping contracts under:
These contracts allow independent Maatify modules to expose route-to-permission requirements without depending on AdminKernel or any application-specific security implementation.
This keeps modules reusable and decoupled while allowing the application or kernel layer to aggregate permission maps and convert them into its own authorization model.
Defining Permission Requirements
Use PermissionRequirementDefinition to describe the permission requirement for a route.
Providing a Permission Map from a Module
A module can expose its route permission map by implementing PermissionMapProviderInterface.
Exposing Permission Map Providers from a Package
A package or module-level entry point may implement ProvidesPermissionMapsInterface to expose one or more permission map providers.
The consuming application or kernel layer is responsible for collecting these providers and converting the neutral definitions into its own authorization objects.
Further Documentation
- How to Use - Practical integration instructions.
- Changelog - History and evolution of the module.
Documentation Book
Comprehensive architecture and integration guides are available in the Book:
| Chapter | Description |
|---|---|
| Table of Contents | Main entry point for the documentation book. |
| 01. Overview | The philosophy and purpose behind SharedCommon. |
| 02. Architecture | Layering and separation of interfaces and infrastructure. |
| 03. Domain Objects | Core contracts representing the system state context. |
| 04. Clock Abstraction | Why the ClockInterface is crucial for testability and consistency. |
| 05. Integration Patterns | Real-world DI container wiring and cross-module usage. |
| 06. Extension Points | How to provide application-specific context implementations. |
