Pulsar

Appearance

Service commands ​

These package commands generate Service-layer roots and delivery types. Their syntax and output patterns are generated from the manifest.

make:command

Create a new application console command

Synopsis

make:command [--signature SIGNATURE] [--] <name> <module> <service>

Arguments and options

  • name — The name of the command
  • module — The name of the module
  • service — The name of the service
  • --signature=VALUE — The Artisan command signature

Use

Prerequisites
Use a valid generated type name and create its required parent Service or Domain first.
Effect
Creates the selected generated application type at the manifest-defined path.
Generated paths or files
app/Pulsar/Services/{Service}/Modules/{Module}/Commands/{Name}.php
Success output shape
Reports the command outcome; file generators report their generated location.
Expected failures
Invalid names, missing parents, and duplicate target files fail without replacing an existing file.
Overwrite policy
Existing generated files are not overwritten.

Checked example

pulsar make:command ReconcileLedger Billing Internal --signature=billing:reconcile

See the related reference.

make:controller

Create a new Controller in a Service Module

Synopsis

make:controller [-r|--resource] [--] <name> <module> <service>

Arguments and options

  • name — The name of the controller
  • module — The name of the module
  • service — The name of the service
  • -r, --resource — Generate a resourceful controller with CRUD methods

Use

Prerequisites
Use a valid generated type name and create its required parent Service or Domain first.
Effect
Creates the selected generated application type at the manifest-defined path.
Generated paths or files
app/Pulsar/Services/{Service}/Modules/{Module}/Controllers/{Name}.php
Success output shape
Reports the command outcome; file generators report their generated location.
Expected failures
Invalid names, missing parents, and duplicate target files fail without replacing an existing file.
Overwrite policy
Existing generated files are not overwritten.

Checked example

pulsar make:controller OrderController Orders Admin --resource

See the related reference.

make:job

Create a new workflow-entrypoint job

Synopsis

make:job <name> <module> <service>

Arguments and options

  • name — The name of the job
  • module — The name of the module
  • service — The name of the service

Use

Prerequisites
Use a valid generated type name and create its required parent Service or Domain first.
Effect
Creates the selected generated application type at the manifest-defined path.
Generated paths or files
app/Pulsar/Services/{Service}/Modules/{Module}/Jobs/{Name}.php
Success output shape
Reports the command outcome; file generators report their generated location.
Expected failures
Invalid names, missing parents, and duplicate target files fail without replacing an existing file.
Overwrite policy
Existing generated files are not overwritten.

Checked example

pulsar make:job Example Orders Admin

See the related reference.

make:operation

Create a new operation class

Synopsis

make:operation <name> <module> <service>

Arguments and options

  • name — The name of the operation
  • module — The name of the module
  • service — The name of the service

Use

Prerequisites
Use a valid generated type name and create its required parent Service or Domain first.
Effect
Creates the selected generated application type at the manifest-defined path.
Generated paths or files
app/Pulsar/Services/{Service}/Modules/{Module}/Operations/{Name}.php
Success output shape
Reports the command outcome; file generators report their generated location.
Expected failures
Invalid names, missing parents, and duplicate target files fail without replacing an existing file.
Overwrite policy
Existing generated files are not overwritten.

Checked example

pulsar make:operation Example Orders Admin

See the related reference.

make:request

Create a new Form Request in a Service Module

Synopsis

make:request <name> <module> <service>

Arguments and options

  • name — The name of the request
  • module — The name of the module
  • service — The name of the service

Use

Prerequisites
Use a valid generated type name and create its required parent Service or Domain first.
Effect
Creates the selected generated application type at the manifest-defined path.
Generated paths or files
app/Pulsar/Services/{Service}/Modules/{Module}/Requests/{Name}.php
Success output shape
Reports the command outcome; file generators report their generated location.
Expected failures
Invalid names, missing parents, and duplicate target files fail without replacing an existing file.
Overwrite policy
Existing generated files are not overwritten.

Checked example

pulsar make:request Example Orders Admin

See the related reference.

make:resource

Create a new service-layer HTTP resource

Synopsis

make:resource [--collection] [--] <name> <module> <service>

Arguments and options

  • name — The name of the resource
  • module — The name of the module
  • service — The name of the service
  • --collection — Generate a resource collection

Use

Prerequisites
Use a valid generated type name and create its required parent Service or Domain first.
Effect
Creates the selected generated application type at the manifest-defined path.
Generated paths or files
app/Pulsar/Services/{Service}/Modules/{Module}/Resources/{Name}.php
Success output shape
Reports the command outcome; file generators report their generated location.
Expected failures
Invalid names, missing parents, and duplicate target files fail without replacing an existing file.
Overwrite policy
Existing generated files are not overwritten.

Checked example

pulsar make:resource OrderResource Orders Admin --collection

See the related reference.

make:service

Create a new Service

Synopsis

make:service [--web] [--] <name>

Arguments and options

  • name — The name of the service
  • --web — Generate session-backed browser routes

Use

Prerequisites
Use a valid, unused architectural name.
Effect
Creates the named architectural root and its generated support files.
Generated paths or files
app/Pulsar/Services/{Service}/Modules/.gitkeepapp/Pulsar/Services/{Service}/Providers/RouteServiceProvider.phpapp/Pulsar/Services/{Service}/Providers/{Service}ServiceProvider.phpapp/Pulsar/Services/{Service}/Routes/api.phpapp/Pulsar/Services/{Service}/Routes/web.php
Success output shape
Reports the command outcome; file generators report their generated location.
Expected failures
Duplicate or invalid names fail before a partial generated structure is written.
Overwrite policy
Existing generated roots are not overwritten.

Checked example

pulsar make:service Admin --web

See the related reference.

make:use-case

Create a new UseCase in a Service Module

Synopsis

make:use-case <name> <module> <service>

Arguments and options

  • name — The name of the use case
  • module — The name of the module
  • service — The name of the service

Use

Prerequisites
Use a valid generated type name and create its required parent Service or Domain first.
Effect
Creates the selected generated application type at the manifest-defined path.
Generated paths or files
app/Pulsar/Services/{Service}/Modules/{Module}/UseCases/{Name}.php
Success output shape
Reports the command outcome; file generators report their generated location.
Expected failures
Invalid names, missing parents, and duplicate target files fail without replacing an existing file.
Overwrite policy
Existing generated files are not overwritten.

Checked example

pulsar make:use-case Example Orders Admin

See the related reference.