Uploaded image for project: 'eZ Publish / Platform'
  1. eZ Publish / Platform
  2. EZP-21718

Implement a custom RouteLoader for internal and custom REST routes

    Details

      Description

      Currently internal eZ routes are imported in main ezpublish/config/routing.yml.

      _ezpublishRoutes:
          resource: "@EzPublishCoreBundle/Resources/config/routing/internal.yml"
       
      _ezpublishLegacyRoutes:
          resource: "@EzPublishLegacyBundle/Resources/config/routing.yml"
       
      _ezpublishRestRoutes:
          resource: "@EzPublishRestBundle/Resources/config/routing.yml"
          prefix:   %ezpublish_rest.path_prefix%
      

      Internal routes can hence be deactivated, which is something we don't want.

      Another thing is that custom REST routes are currently only identified by the %ezpublish_rest.path_prefix%, which is not very clean either.

      A good solution would be to implement route loaders, having different types (for core, legacy and rest).

      For REST, an ez_rest type would make custom REST routes easy to identify.

        Issue Links

          Activity

          Hide
          Bertrand Dunogier added a comment -

          Is this really valid ? After looking into route loaders, they do not allow a bundle to add routes without the user explicitely adding them to his app routes (and that's on purpose).

          Show
          Bertrand Dunogier added a comment - Is this really valid ? After looking into route loaders, they do not allow a bundle to add routes without the user explicitely adding them to his app routes (and that's on purpose).

            People

            • Assignee:
              Unassigned
              Reporter:
              Jérôme Vieilledent (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: