Merge pull request #367 from lyrixx/path-resolver

Fixed doc about "path_segment_name_generator" for v2.1+

Author: dunglas

core/operation-path-naming.md

@@ -7,19 +7,19 @@ Pre-registered resolvers are available and can easily be overridden.
 
 There are two pre-registered operation path naming services:
 
-Service name                                      | Entity name  | Path result
---------------------------------------------------|--------------|----------------
-`api_platform.operation_path_resolver.underscore` | `MyResource` | `/my_resources`
-`api_platform.operation_path_resolver.dash`       | `MyResource` | `/my-resources`
+Service name                                          | Entity name  | Path result
+------------------------------------------------------|--------------|----------------
+`api_platform.path_segment_name_generator.underscore` | `MyResource` | `/my_resources`
+`api_platform.path_segment_name_generator.dash`       | `MyResource` | `/my-resources`
 
-The default resolver is `api_platform.operation_path_resolver.underscore`.
+The default resolver is `api_platform.path_segment_name_generator.underscore`.
 To change it to the dash resolver, add the following lines to `app/config/config.yml`:
 
 ```yaml
 # app/config/config.yml
 
 api_platform:
-    default_operation_path_resolver: 'api_platform.operation_path_resolver.dash'
+    path_segment_name_generator: api_platform.path_segment_name_generator.dash
 ```
 
 ## Create a Custom Operation Path Resolver
@@ -75,5 +75,5 @@ services:
 # app/config/config.yml
 
 api_platform:
-    default_operation_path_resolver: 'AppBundle\PathResolver\NoSeparatorsOperationPathResolver'
+    path_segment_name_generator: 'AppBundle\PathResolver\NoSeparatorsOperationPathResolver'
 ```