Chapters

48 Chapters | 5:13:28 |

01

App & Test Setup

7:44
02

Data Persister Decoration

6:48
03

Decorating Data Persisters vs Context Builders

8:54
04

Custom Logic Only for some Operations

5:02
05

Publishing a Listing

6:02
06

Detecting the "Published" State Change

9:08
07

Validating Who/When Can Publish

8:22
08

Publish State Change Validator Logic

8:26
09

Completely Custom Field via a Data Provider

9:19
10

Leveraging the Doctrine Data Provider

5:27
11

Adding & Populating the Custom Field

5:10
12

Custom Item Data Provider

6:57
13

Setting a Custom Field Via a Listener

5:32
14

Core Listeners & Accessing the "Resource" Objects

4:37
15

Doctrine postLoad Listener

8:03
16

Completely Custom Resource

5:25
17

Custom Resource Data Provider

6:40
18

Property Metadata

6:20
19

Why/When a Many Relation is IRI Strings vs Embedded

5:19
20

Collection "Types" and readableLink

7:12
21

Custom Resource GET Item

5:50
22

Custom Paginator

7:04
23

Pagination Context

7:09
24

Custom Resource PUT Operation

5:19
25

Custom Filter, getDescription() & properties

7:09
26

Custom Filter Logic for Entities

8:25
27

Custom Filter for Custom Resources

7:49
28

Custom Filter apply()

8:15
29

Filter Class Arguments

4:26
30

Filter Autowiring

5:46
31

Output DTO Class

4:40
32

DTO Data Transformer

5:31
33

Output Properties & Metadata

7:14
34

DTO Quirks

5:23
35

DTO Quirks: Embedded Objects

6:37
36

Input DTO Class

7:16
37

Input DTO: Denormalizing IRI Strings

5:33
38

Input Data Transformer

4:24
39

Input DTO Update Problems

6:38
40

DTO Input "Initializer"

6:41
41

DTO Input Initializer Logic

6:19
42

DTO Class Organization

5:12
43

Type Validation

7:29
44

Input DTO Validation

5:43
45

UUID's

7:29
46

UUID as a API Identifier

5:16
47

Setting the UUID on POST

5:15
48

UUID Quirk with "id" Name

7:09

This tutorial has a new version, check it out!

> Symfony 5 > API Platform 2 Part 3: Custom Resources

Buy Access to Course

33.

Output Properties & Metadata

|

Autoplay

Keep on Learning!

If you liked what you've learned so far, dive in! Subscribe to get
access to this tutorial plus video, code and script downloads.

Start your All-Access Pass

Buy just this tutorial for $12.00

Previous Chapter

Next Chapter

With a Subscription, click any sentence in the script to jump to that part of the video!

Login Subscribe

Login or register to check out the script

7 Comments

Sort By

Login or Register to join the conversation

Petru L. 5 years ago

Hey Ryan, i was wondering if there's a way to only add the fields that needs to be processed differently, in the transformer. For example, i have a File entity with the usual fields: name, extension, mimetype, etc ( those are also db columns ) and beside those i also have a file property that isn't a db column. This file is actually a resource that is sent via api in a multipart format ( or maybe just a link to the resource ) and then i process it.( i save it in s3, then save only the s3 path in my db ). Can i force api platform to use the normal fields on read/write from the entity and use only the file property from the FileInput ( and FileInputDataTransformer), since the only time i need the file field is when i save it to s3 and save its properties to db

|

Petru L. Petru L. 5 years ago edited

Quick mention: i've defined groups for serialization/deserialization in my entity and due to that fact, if i leave them in my entity without adding them in the Dto class, it triggers an error: Can't get a way to read the property \"extension\" in class \"App\\Data\\File Output\"

|

weaverryan SFCASTS Petru L. 5 years ago edited

Hey Petru L.!

Hmm. What if you *don't* create an input DTO at all. Instead, add the non-persisted "file" property to your entity (it sounds like you already have this) and use a custom data persister to handle processing the resource/link on that "file" property (the saving it to s3 part).

Would that work? Or am I missing a complication? With just one "weird" field, this is the first idea that popped into my head. Input/output DTO's are more of a headache, unless you have a lot of differences between your input/output and how your entity looks.

Cheers!

|

Petru L. weaverryan 5 years ago

Yeah, it looks like data persister might be the way to go but while this solves my POST problem, i got a similar issue with the GET. For example, after a certain file has been saved into db ( and in s3 ), one user may request that file, and the path field in my db contain only the relative path to the file, i need to transform it into the absolute path and not just that, maybe the user wants a thumbnail of it, and so i'll have to serve the liip-imagine cached thumbnail path, or maybe he request the image of a certain resolution, and i'll have to do some more parsing there too. Should i stick with the DTO for the output or is something better for this case? Thank you

|

weaverryan SFCASTS Petru L. 5 years ago edited

Hey Petru L.!

> i got a similar issue with the GET. For example, after a certain file has been saved into db ( and in s3 ), one user may request that file, and the path field in my db contain only the relative path to the file, i need to transform it into the absolute path

No problem :). Add one (or some) non-persisted fields and use a custom data provider to supply those :). We talk about this a bit earlier in the tutorial - https://symfonycasts.com/sc...

Cheers!

|

Petru L. Petru L. 5 years ago edited

Petru L. , came across another problem... I'm trying to send a multipart request through api and so i enabled the multipart type in api_platform.yaml, then it said it couldn't deserialized and so i turn the deserialization off in the entity and then i got stuck at:

Could not resolve argument $data of "api_platform.action.post_collection()", maybe you forgot to register the controller as a service or missed tagging it with the "controller.service_arguments"?

. In the api platform guide to upload file, they create a custom action for it: https://api-platform.com/do.... So maybe that's the only way to do it??

|

weaverryan SFCASTS Petru L. 5 years ago edited

Hey Petru L.!

I've never used API Platform's native file upload tools. But yes, my guess is that the custom action is needed... when you turn deserialization off, then there is no "$data" on the request attributes... and I think the normal, core controller fails. I'm doing a bit of guessing on this, but it would make sense to me :).

Cheers!

|

This tutorial also works great with API Platform 2.6.

Api Platform 2.5 Symfony 5

What PHP libraries does this tutorial use?

// composer.json
{
    "require": {
        "php": ">=8.2",
        "ext-ctype": "*",
        "ext-iconv": "*",
        "api-platform/core": "^2.1", // v2.5.10
        "composer/package-versions-deprecated": "^1.11", // 1.11.99
        "doctrine/annotations": "^1.0", // 1.12.1
        "doctrine/doctrine-bundle": "^2.0", // 2.1.2
        "doctrine/doctrine-migrations-bundle": "^3.0", // 3.0.2
        "doctrine/orm": "^2.4.5", // 2.8.2
        "nelmio/cors-bundle": "^2.1", // 2.1.0
        "nesbot/carbon": "^2.17", // 2.39.1
        "phpdocumentor/reflection-docblock": "^3.0 || ^4.0 || ^5.0", // 5.2.2
        "ramsey/uuid-doctrine": "^1.6", // 1.6.0
        "symfony/asset": "5.1.*", // v5.1.5
        "symfony/console": "5.1.*", // v5.1.5
        "symfony/debug-bundle": "5.1.*", // v5.1.5
        "symfony/dotenv": "5.1.*", // v5.1.5
        "symfony/expression-language": "5.1.*", // v5.1.5
        "symfony/flex": "^1.1", // v1.21.6
        "symfony/framework-bundle": "5.1.*", // v5.1.5
        "symfony/http-client": "5.1.*", // v5.1.5
        "symfony/monolog-bundle": "^3.4", // v3.5.0
        "symfony/security-bundle": "5.1.*", // v5.1.5
        "symfony/twig-bundle": "5.1.*", // v5.1.5
        "symfony/validator": "5.1.*", // v5.1.5
        "symfony/webpack-encore-bundle": "^1.6", // v1.8.0
        "symfony/yaml": "5.1.*" // v5.1.5
    },
    "require-dev": {
        "doctrine/doctrine-fixtures-bundle": "^3.3", // 3.3.2
        "symfony/browser-kit": "5.1.*", // v5.1.5
        "symfony/css-selector": "5.1.*", // v5.1.5
        "symfony/maker-bundle": "^1.11", // v1.23.0
        "symfony/phpunit-bridge": "5.1.*", // v5.1.5
        "symfony/stopwatch": "5.1.*", // v5.1.5
        "symfony/twig-bundle": "5.1.*", // v5.1.5
        "symfony/web-profiler-bundle": "5.1.*", // v5.1.5
        "zenstruck/foundry": "^1.1" // v1.8.0
    }
}

Previous Chapter

Next Chapter