Configuration

Configuration options for WPZylos Routing.

Service Provider Options

The RoutingServiceProvider automatically loads route files from standard locations.

Route File Locations

REST API Namespace

The REST API namespace is derived from your plugin context:

// Plugin slug: "my-plugin"
// API version: "v1"
// Namespace: "my-plugin/v1"
// Endpoint: /wp-json/my-plugin/v1/...

Container Bindings

The service provider registers these bindings:

WordPress Hooks

Routes are dispatched via these hooks:

Middleware Configuration

Middleware classes must implement a handle method:

public function handle($request, callable $next): mixed
{
    // Before
    $response = $next($request);
    // After
    return $response;
}

Nonce Configuration

AJAX nonce actions are prefixed with the plugin prefix:

// Plugin prefix: "myplugin_"
// Action: "save_settings"
// Nonce action: "myplugin_save_settings"

Rewrite Rules

Frontend routes automatically register WordPress rewrite rules on activation:

// Pattern: /products/{id}
// Rewrite: ^products/([^/]+)/?$
// Target: index.php?myplugin_route=/products/{id}

Flush rewrite rules after route changes:

WPAdapter::flush();