Skip to content

Commit 4d4a7f0

Browse files
authored
fix: don't mention outdated Data Transformers (#1675)
1 parent a887fae commit 4d4a7f0

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

core/extending.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,9 +15,9 @@ The following tables summarizes which extension point to use depending on what y
1515
| [State Processors](state-processors) | custom business logic and computations to trigger before or after persistence (ex: mail, call to an external API...) |
1616
| [Normalizers](serialization.md#decorating-a-serializer-and-adding-extra-data) | customize the resource sent to the client (add fields in JSON documents, encode codes, dates...) |
1717
| [Filters](filters.md) | create filters for collections and automatically document them (OpenAPI, GraphQL, Hydra) |
18-
| [Serializer Context Builders](serialization.md#changing-the-serialization-context-dynamically) | Changing the Serialization context (e.g. groups) dynamically |
18+
| [Serializer Context Builders](serialization.md#changing-the-serialization-context-dynamically) | change the Serialization context (e.g. groups) dynamically |
1919
| [Messenger Handlers](messenger.md) | create 100% custom, RPC, async, service-oriented endpoints (should be used in place of custom controllers because the messenger integration is compatible with both REST and GraphQL, while custom controllers only work with REST) |
20-
| [DTOs and Data Transformers](dto.md) | use a specific class to represent the input or output data structure related to an operation |
20+
| [DTOs](dto.md) | use a specific class to represent the input or output data structure related to an operation |
2121
| [Kernel Events](events.md) | customize the HTTP request or response (REST only, other extension points must be preferred when possible) |
2222

2323
## Doctrine Specific Extension Points

0 commit comments

Comments
 (0)