mirror of
https://github.com/wallabag/wallabag.git
synced 2024-11-14 13:01:09 +00:00
ee32248f43
When we remove the client, we should ensure that access_token are also removed. To ensure that, I created a test that generated an access_token. So when we remove the client, this association should be cascaded and shouldn’t generate an error. Also I moved some Api related stuff to the ApiBundle (like the developer controler and ClientType form)
54 lines
1.2 KiB
YAML
54 lines
1.2 KiB
YAML
wallabag_annotation:
|
|
type : rest
|
|
resource: "@WallabagAnnotationBundle/Resources/config/routing_annotations.yml"
|
|
|
|
wallabag_import:
|
|
resource: "@WallabagImportBundle/Controller/"
|
|
type: annotation
|
|
prefix: /import
|
|
|
|
wallabag_user:
|
|
resource: "@WallabagUserBundle/Controller/"
|
|
type: annotation
|
|
prefix: /users
|
|
|
|
wallabag_api:
|
|
resource: "@WallabagApiBundle/Controller/"
|
|
type: annotation
|
|
prefix: /
|
|
|
|
wallabag_api:
|
|
resource: "@WallabagApiBundle/Resources/config/routing.yml"
|
|
prefix: /
|
|
|
|
app:
|
|
resource: "@WallabagCoreBundle/Controller/"
|
|
type: annotation
|
|
|
|
doc-api:
|
|
resource: "@NelmioApiDocBundle/Resources/config/routing.yml"
|
|
prefix: /api/doc
|
|
|
|
rest :
|
|
type : rest
|
|
resource : "routing_rest.yml"
|
|
prefix : /api
|
|
|
|
homepage:
|
|
path: "/{page}"
|
|
defaults:
|
|
_controller: WallabagCoreBundle:Entry:showUnread
|
|
page : 1
|
|
requirements:
|
|
page: \d+
|
|
|
|
fos_user:
|
|
resource: "@FOSUserBundle/Resources/config/routing/all.xml"
|
|
|
|
fos_oauth_server_token:
|
|
resource: "@FOSOAuthServerBundle/Resources/config/routing/token.xml"
|
|
|
|
craue_config_settings_modify:
|
|
path: /settings
|
|
defaults:
|
|
_controller: CraueConfigBundle:Settings:modify
|