developer.jelix.org is not used any more and exists only for history. Post new tickets on the Github account.
developer.jelix.org n'est plus utilisée, et existe uniquement pour son historique. Postez les nouveaux tickets sur le compte github.

Changes between Version 2 and Version 3 of rfc/new-url-routing


Ignore:
Timestamp:
Sep 14, 2012, 11:23:00 AM (8 years ago)
Author:
laurentj
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • rfc/new-url-routing

    v2 v3  
    1919  * suppress the plugin system for URLs
    2020  * we keep the significant url engine.
    21   * we improve the engine to allow to declare some url like we had for basic_significant (so we won't have to declare url for all methods of all controllers. ex:
     21  * we improve the engine to allow to declare that it should support basic significant url, so we won't have to declare url for all methods of all controllers. We could activate it with a simple basicSignificant attribute. ex:
    2222
    2323{{{
     24   <entrypoint type="classic" name="index" default="true" basicSignificant="true">
    2425
    25     <url pathinfo="/my/path/:_module/:_controller/:_method" />
    26     <url pathinfo="/my/path2/:_controller/:_method" module="monmodule" />
    27     <url pathinfo="/my/path3/:_method" module="monmodule" action="controller" />
     26       <url .../>
     27   </entrypoint>
    2828
    2929}}}
    30 So we would have reserved parameters: _module, _controller, _method.
    3130
    32 What about current module and action parameters ?
    33 I propose to not support anymore module and action parameter readed from the URL (except for "overrided" action in urls.xml). However, we could generate module and action parameter to keep compatibility in controllers (for "old" controllers or zone or whatever) that use the module and/or action parameters. We could deprecate this behavior.
     31    If a given url does not correspond to url declared inside the entrypoint, jUrl tries to map it to "/:module/:controller/:method", as the basic_significant engine did. Only one entrypoint is allowed to support basic_significant, else jUrl::get() could not know on which entry point it should take to generate the url.
     32
     33    * remove the "module" and "action" GET parameters in urls, except for "overrided" action in urls.xml. However, we could continue to have "module" and "action" parameters in the list of request parameters, in internal code, to keep  compatibility with all components (such as controllers with "$this->param('module')"). However we could deprecate this behavior (and emit a notice?).
    3434
    3535see [ticket:1223].