Pckg Documentation
Pckg Documentation
  • About
  • Concept
  • Start
  • Deployment
  • Tests
  • Ecosystem
    • Docker images
    • Skeleton
  • Core packages
    • Auth
    • Cache
    • Collection
    • Concept
    • Database
      • Repository
        • Driver
      • Entity
        • Relations
        • Query
      • Record
        • Fields
        • Model
      • Events
      • Extensions
    • Framework
      • Environment
        • Console
        • Development
        • Production
        • Test
      • Application
      • Providers
      • Config
      • Router
      • Request
      • Response
      • Controller
        • Middleware
        • Afterware
      • View
      • Events
      • Exception
    • Generic
      • Dynamic
      • Generic
      • Maestro
    • Htmlbuilder
      • Elements
        • Form
        • Fields
      • Datasources
      • Validators
      • Decorators
    • Locale
    • Mail
      • Drivers
      • Template
      • Mail
    • Manager
      • Asset manager
      • SEO manager
      • Meta manager
      • Upload manager
      • Vue manager
      • Job manager
      • Locale manager
      • Page manager
    • Migrator
      • Migrations
      • Fields
    • Queue
      • Driver
      • Publisher
      • Subscriber
    • Storage
      • Driver
      • Media
    • Translator
  • More packages
    • API
    • HTTP QL
      • Read
      • Write
      • Uploads
    • Task
      • Async
    • Websocket
      • Server
      • Client
  • Frontend
    • Helpers JS
    • Helpers CSS
  • Extras
    • Parser
    • Payment
    • Tenant
Powered by GitBook
On this page
  • Routes
  • Autoloaders
  • Classmaps
  • Providers
  • Apps
  • Consoles
  • Assets
  • Paths
  • Middlewares
  • Afterwares
  • View objects
  • Listeners
  • Jobs

Was this helpful?

  1. Core packages
  2. Framework

Providers

Provider is a class that defines all features from the domain. This way you can easily activate or deactivate features and group them for easier maintenance.Many aspects of framework are designed as providers, for example Environment and Application.

You can group:

  • (sub-)providers

  • services

  • routes

  • listeners (for events)

  • middlewares and afterwares

  • console commands

  • jobs

  • assets (frontend - css & js)

  • translations

In addition to that, a provider can also register:

  • autoloaders and classmaps

  • reuse other apps (which are also providers)

  • view paths (for twig) and view objects (available in tempalte engines)

Providers are registered in the run app step of the request lifecycle when the Config is already initialized.

Routes

Autoloaders

Classmaps

Providers

Apps

Consoles

Assets

Paths

Middlewares

Afterwares

View objects

Listeners

Jobs

PreviousApplicationNextConfig

Last updated 2 years ago

Was this helpful?