Skip to content

Action Controller 9.0.0

Choose a tag to compare

View all tags
@stakach stakach released this 08 Oct 04:17
· 10 commits to master since this release
v9.0.0
602925c
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Action Controller 9.0.0 adds composable applications, replacement-base mounts and shared HTTP/OpenAPI/MCP catalogs.

New capabilities

  • Serve a controller subtree through App::Base.handler, an independent HTTP::Handler. Route misses continue downstream; matched actions retain their response, including intentional 404s.
  • Select application roots with AC::Server.compose(...), or create independent AC::Composition instances. Each server flattens its placements into one routing table.
  • Mount controller or application subtrees beneath a host base, including nested, repeated and parameterized mounts. Public paths are shared by HTTP routing, OpenAPI, MCP and spec helpers.
  • Generate unified OpenAPI definitions and a global MCP server, while preserving mounted controller MCP endpoints and session-bound parameters.
  • Generate mounted URLs with route_path inside actions and composition.url_for outside requests. Existing class URL helpers retain their original paths.

Performance

A lazy trie matcher avoids copying static path segments and allocates captures only after a successful unescaped match. Local release benchmarks show common dynamic lookups 10–16% faster, glob lookup about 46% faster, zero allocated bytes on trie misses and 32–64 fewer bytes for ordinary dynamic requests. Warmed single-handler and mounted fixtures show no consistent dispatch regression. These results are workload-specific; handler chains add a lookup on each miss and escaped paths retain the original matcher.

Upgrade notes

Existing automatic discovery and template startup remain supported. For unified composition, require reusable controller libraries and declare AC::Server.compose(App::Base, OtherApp::Base) once in config.cr. Reusable libraries should keep executable startup and global configuration separate.

Explicit compositions and mounts validate conflicting public routes, including equivalent parameterized routes and implicit HEAD operations. Mounted controllers keep their own filters; mounting alone does not apply the host controller's filters. The host owns global middleware, sessions, MCP settings and UI assets.

Regenerate MCP description files with --mcp or write_description when adopting composition or changing mounts to retain source comments. Mismatched composed descriptions are regenerated from compiled metadata; legacy descriptions remain supported for ordinary apps.

See the composition API and examples and reproducible benchmark results.

Assets 2
Loading