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
  • Concept
  • Provider
  • Request timeline
  • Context
  • Read more

Was this helpful?

Concept

PreviousAboutNextStart

Last updated 1 year ago

Was this helpful?

Concept

There are only two the most important concepts of the framework:

  • Context - as a dependency container, it is responsible for resolving dependencies

  • Provider - groups your domain features

Provider

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.

You can read more about Provider under .

Request timeline

Whole website or application is executed in few simple steps.

  • Create context

  • Create environment

    • Error reporting

    • Exception handling

    • Path definition - see path()

    • Load root config - see config()

  • Create, init and run app

    • Parse app config

    • Set localization

    • Init database connections and routing

    • Register main provider

    • Init session, response, request and assets

    • Run request - this is only thing you need to take care of :)

    • Return response

Context

A global context holds singletones and registers resolvers which automatically resolves an instance of the requested class or interface.

Read more

You can read more about Context under .

Now that you're familiar with core concepts, directory structure and request timeline, proceed with the section where you will learn about how to register and implement your domain features.

Packages > Framework > Providers
Packages > Concept
Quick start