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

04.

Custom Logic Only for some Operations

|

Autoplay

Previous Chapter

Next Chapter

Login or register to check out the script

6 Comments

Sort By

Login or Register to join the conversation

Bernard A. 4 years ago edited

Hi
A couple of things:
First, I work mostly with graphql on API-Platform and would appreciate if you create a specific tutorial for that.

Secondly, with API-Platform graphql, I would normally do this type of customization per/post persist on the stages.
Is there any downside of using stages as opposed to data persisters? Why use one or the other? Thanks.

Code example on src/Stages/DeserializeStage.php


....

if ($resourceClass === 'App\Entity\Ad' && $operationName === 'create') {
       $deserializeObject->setUser($user);
       $deserializeObject->setIsActive(true);
      // when user creating ad offer, add providedCategory if not already exists
       if ($deserializeObject->getIsOffer()) {
           // check if user providedCategory already include ad category
           if (!$user->getProvidedCategories()->contains($deserializeObject->getCategory()) ) {
                 $user->addProvidedCategory($deserializeObject->getCategory());
           }
            }
.....

|

weaverryan SFCASTS Bernard A. 4 years ago edited

Hey Bernard A. !

Nice to chat with you :). I believe the short answer is this: data persisters work for graphql or REST whereas stages are graphql only. So, if you're using graphql (caveat: I'm not very familiar with API Platform's GraphQL), there shouldn't really be any advantage or disadvantage. Frequently in the API Platform docs, they recommend solutions that "work everywhere" vs GraphQL or REST-specific solutions... just for simplicity I think :). For REST, iirc, the events system (iirc) is unique to it (and not included in GraphQL).

Cheers!

|

Bernard A. weaverryan 4 years ago

Hi
Thanks for your reply! Though you elegantly sidestepped the issue of the graphql tutorial.:)

|

weaverryan SFCASTS Bernard A. 4 years ago

Lol, guilty! I can't remember if I did that on purpose or not! I'll add your vote to our internal list... but probably not something we would do anytime too soon. However, we will need to, at some point in the not TOO distant future, refresh our API Platform tutorials. And when we do, that'd be the time to do it.

Cheers!

1 |

Anton B. 5 years ago

@weaverryan can you please answer this question?
https://stackoverflow.com/q...

|

weaverryan SFCASTS Anton B. 5 years ago

Hey Anton!

Hmm, yea, I’m not sure! It sounds like the key is security, since you mentioned that removing a role fixes it. The question would be: can you get it to work with zero security? And can you also successfully trigger a 403 by using a role your user doesn’t have? You want to first see if either the success response or 403 response is causing the problem.

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