Ticket #683 (closed task: fixed)

Opened 10 months ago

Last modified 3 months ago

Deprecate core.use_routing in favor of a routing config parameter

Reported by: david Owned by: david
Priority: high Milestone: 1.0
Component: _OTHER_ Version:
Severity: major Keywords:
Cc: Patch attached: no

Description (last modified by david) (diff)

It always runs, anyway. But the actual idea is that you could then switch routing off for, say, the CLI context (which means it falls back to $argv or whatever instead of using parsing magic), but keep it on for web:

<routing class="AgaviConsoleRouting">
  <parameter name="enabled">false</parameter>
</routing>

The calls to this would look like the following:

$ro->getParameter('enabled', AgaviConfig::get('core.use_routing'));

So we have full BC. Maybe even a dedicated method? It's not used outside the routing classes, either.

Attachments

Change History

Changed 10 months ago by david

  • description modified (diff)

Changed 10 months ago by david

  • status changed from new to closed
  • resolution set to fixed

(In [2284]) Deprecated directive "core.use_routing" in favor of a routing config parameter ("enabled"), closes #683

Changed 10 months ago by david

There's AgaviRouting::isEnabled() now, btw.

Changed 3 months ago by david

(In [2657]) changelog entry forgotten in [2284], refs #683

Add/Change #683 (Deprecate core.use_routing in favor of a routing config parameter)

Author



Action
as closed
Next status will be 'reopened'
 
Note: See TracTickets for help on using tickets.