Repository navigation
Document the 3.1 app lifecycle, the runtime events and the console boot - #143
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents the 3.1 app lifecycle as it is on the framework's
masterafter quantum-php/framework#590 (#589) and quantum-php/framework#591 (#538).What changed
packages/app/architecture.md: the factory boots the adapter withboot(); a stage can end a run withstop()and the web runtime sends the response in a closing stage; "Hooking into the boot" becomes "Hooking into the running app", with a helper-file example onweb.send.beforeandconsole.command.beforeand why the boot fires no events; the new console boot order (core commands before the environment, your commands last); where the stages live.packages/app/contracts.md: newAppInterfacesection (boot()/start(), creating an adapter does not boot it, no adapter catches exceptions); the run state onAppContext;getBootFailure()andWebContext::stop()removed from the runtime contexts; the pipeline rules (stop, closing stage); new "Lifecycle events" section with the seven runtime stages, their events, and which events fire for a matched route, OPTIONS, no route and a stage that throws.packages/app/adapters.md: the console description and the lifecycle link.cli/qt-command-line-tool.md: the boot steps in their new order; "When the boot fails" becomes "Commands without a working environment": on a missing or malformed.env,core:env,listandhelprun and every other command stops with the environment error; theapp:doctorexample is gone, since a project command can no longer run on a broken.env.cli/console-commands.md:$requiresEnvironmentand the new section link.packages/event/overview.md,usage.md,architecture.md: the framework's own events are the request and command events, not boot events.packages/debugger/overview.md,architecture.md: the new stage namespaces.advanced-features/request-lifecycle.md: one sentence pointing to the runtime events.Changed paths
v3.0/packages/app/architecture.mdv3.0/packages/app/contracts.mdv3.0/packages/app/adapters.mdv3.0/cli/qt-command-line-tool.mdv3.0/cli/console-commands.mdv3.0/packages/event/overview.mdv3.0/packages/event/usage.mdv3.0/packages/event/architecture.mdv3.0/packages/debugger/overview.mdv3.0/packages/debugger/architecture.mdv3.0/advanced-features/request-lifecycle.mdSUMMARY.md: no change.