Chapters

36 Chapters | 3:44:20 |

01

Setup & Ways to Extend API Platform

4:39
02

State Providers, Processors & a Custom Field

4:49
03

Decorating the Core State Provider

4:47
04

Decorating the CollectionProvider

7:12
05

Simpler State Processor

5:47
06

Running Code "On Publish"

6:05
07

Totally Custom Resource

4:19
08

Custom Resource State Provider

5:04
09

Using a Custom (Date) Identifier

7:35
10

Custom Resource Item Provider

3:26
11

Custom Resource State Processor

6:48
12

Relating Custom ApiResources

5:13
13

Embedding Custom DTO's

4:47
14

Pagination on a Custom Resource

8:18
15

User Class Dto

4:24
16

stateOptions + entityClass Magic

10:07
17

Entities, DTO's & The "Central" Object

6:24
18

Provider: Transforming Entities to DTOs

4:47
19

Entity -> DTO Item State Provider

4:11
20

DTO -> Entity State Processor

7:39
21

Leveraging the Core Processor

7:11
22

Controlling Fields without Groups

4:31
23

Other Conditional Field Strategies

6:04
24

DTO Validation & Security

6:13
25

MicroMapper: Central DTO Mapping

10:11
26

Reusable Entity->Dto Provider & Processor

4:11
27

Quick! Create a DragonTreasure DTO

9:51
28

Dtos, Mapping & Max Depth of Relations

8:05
29

Making DragonTreasureApi Writable

7:23
30

DTO & Security

9:39
31

Field Security with Patch

6:17
32

Triggering a "Publish"

4:14
33

Writable Relation Fields

5:09
34

Writing to a Collection Relation

5:08
35

Writable Collection via the PropertyAccessor

6:29
36

Simpler Validator for Checking State Change

7:23

> APIs > API Platform 3 Part 3: Custom Resources

Buy Access to Course

35.

Writable Collection via the PropertyAccessor

|

|

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

4 Comments

Sort By

Login or Register to join the conversation

sujal_k 2 years ago edited

One more question, patch() should update specific data, no? But it seems to replace those two data in the database ( and remove that second one ) but one gets removed (the second one), I mean why should it get removed due to a patch() request? just because we didn't send it during the update

->patch('/api/users/' . $user->getId(), [
                'json' => [
                    'dragonTreasures' => [
                        '/api/treasures/' . $dragonTreasure->getId(),
                        '/api/treasures/' . $dragonTreasure3->getId(),
                    ],
                ],

So, is it removing from the database because when deserializing, it's owner gets set to null, because of the data that's sent ( i.e. dragonTreasures => [ '/api/treasures/1', 'api/treasures/2' ] ) does not get deserialized, and as a result, it's owner is missing ?

|

weaverryan SFCASTS sujal_k 2 years ago edited

Hey @sujal_k!

This longer description of the whole process might help :)

https://symfonycasts.com/screencast/api-platform-extending/collection-relation-setting#comment-32177

Cheers!

|

sujal_k 2 years ago edited

At 5:26 timestamp, when I ran the test, it says:

    `"hydra:description": "An exception occurred while executing a query: SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'owner_id' cannot be null",`

I think I followed it correctly, but it says like that.

Till that dump() just before this failing test, it worked fine.

But when inside DragonTreasure entity, when I set nullable: true, the test passed but in database owner is set to NULL for dragon treasure with id=2

#[ORM\ManyToOne(inversedBy: 'dragonTreasures')]
#[ORM\JoinColumn(nullable: true)]
private ?User $owner = null;

|

weaverryan SFCASTS sujal_k 2 years ago

Hey @sujal_k!

Hmm. Here is what should be happening, maybe it will help:

1) We start with a DragonTreasure with owner set to, let's say user id=2. In the test this user starts with 2 dragon treasures (via lines 61 and 62 of https://symfonycasts.com/screencast/api-platform-extending/collection-relation-setting#codeblock-0bc8575f72).
2) In the test, we send a PATCH request to modify user 2. Specifically, we modify the dragonTreasures property. We set it to an array, but only send the IRI of ONE of the two treasures assigned to this user.
3) When the serializer sees this, it realizes that this use currently has 2 treasures, but we only included the IRI for 1. It actually realizes that we're removing one treasure from this user. And so, it calls $user2->removeDragonTreasure($treasure) where $treasure is the DragonTreasure object whose IRI we did not send.
4) This method removes the treasure from the User.dragonTreasures property. But more importantly, it also calls $treasure->setOwner(null).
5) So at this point, your error makes perfect sense: the serializer is setting the owner to null. So why do we expect the DragonTreasure to be deleted instead? Because of orphanRemoval: https://symfonycasts.com/screencast/api-platform/collections-remove-item. With that in place, if the owner of a DragonTreasure is set to null, instead of saving that, Doctrine deletes the DragonTreasure entirely.

So perhaps orphanRemoval is missing. Or some thing in this process is not being translated through correctly when the DTO -> entity mapping logic happens.

This isn't an answer, but hopefully it can help your debugging :).

Cheers!

|

Symfony 6.3 API Platform 3

What PHP libraries does this tutorial use?

// composer.json
{
    "require": {
        "php": ">=8.1",
        "ext-ctype": "*",
        "ext-iconv": "*",
        "api-platform/core": "3.1.x-dev", // 3.1.x-dev
        "doctrine/annotations": "^2.0", // 2.0.1
        "doctrine/doctrine-bundle": "^2.8", // 2.10.2
        "doctrine/doctrine-migrations-bundle": "^3.2", // 3.2.4
        "doctrine/orm": "^2.14", // 2.16.1
        "nelmio/cors-bundle": "^2.2", // 2.3.1
        "nesbot/carbon": "^2.64", // 2.69.0
        "phpdocumentor/reflection-docblock": "^5.3", // 5.3.0
        "phpstan/phpdoc-parser": "^1.15", // 1.23.1
        "symfony/asset": "6.3.*", // v6.3.0
        "symfony/console": "6.3.*", // v6.3.2
        "symfony/dotenv": "6.3.*", // v6.3.0
        "symfony/expression-language": "6.3.*", // v6.3.0
        "symfony/flex": "^2", // v2.3.3
        "symfony/framework-bundle": "6.3.*", // v6.3.2
        "symfony/property-access": "6.3.*", // v6.3.2
        "symfony/property-info": "6.3.*", // v6.3.0
        "symfony/runtime": "6.3.*", // v6.3.2
        "symfony/security-bundle": "6.3.*", // v6.3.3
        "symfony/serializer": "6.3.*", // v6.3.3
        "symfony/stimulus-bundle": "^2.9", // v2.10.0
        "symfony/string": "6.3.*", // v6.3.2
        "symfony/twig-bundle": "6.3.*", // v6.3.0
        "symfony/ux-react": "^2.6", // v2.10.0
        "symfony/ux-vue": "^2.7", // v2.10.0
        "symfony/validator": "6.3.*", // v6.3.2
        "symfony/webpack-encore-bundle": "^2.0", // v2.0.1
        "symfony/yaml": "6.3.*", // v6.3.3
        "symfonycasts/micro-mapper": "^0.1.0" // v0.1.1
    },
    "require-dev": {
        "doctrine/doctrine-fixtures-bundle": "^3.4", // 3.4.4
        "mtdowling/jmespath.php": "^2.6", // 2.6.1
        "phpunit/phpunit": "^9.5", // 9.6.11
        "symfony/browser-kit": "6.3.*", // v6.3.2
        "symfony/css-selector": "6.3.*", // v6.3.2
        "symfony/debug-bundle": "6.3.*", // v6.3.2
        "symfony/maker-bundle": "^1.48", // v1.50.0
        "symfony/monolog-bundle": "^3.0", // v3.8.0
        "symfony/phpunit-bridge": "^6.2", // v6.3.2
        "symfony/stopwatch": "6.3.*", // v6.3.0
        "symfony/web-profiler-bundle": "6.3.*", // v6.3.2
        "zenstruck/browser": "^1.2", // v1.4.0
        "zenstruck/foundry": "^1.26" // v1.35.0
    }
}

Previous Chapter

Next Chapter