Chapters

39 Chapters | 4:45:13 |

01

Hello API Security + API Docs on Production?

8:55
02

API Auth 101: Session? Cookies? Tokens?

4:05
03

Login with json_login

6:27
04

Authentication Errors

5:55
05

Login Success & the Session

4:28
06

On Authentication Success

7:40
07

Logout & Passing API Data to JS on Page Load

8:49
08

SameSite Cookies & CSRF Attacks

8:06
09

ApiResource access_control

6:03
10

Bootstrapping a Test Suite

4:29
11

Backport the API Platform 2.5 Test Tools

5:01
12

Api Tests & Assertions

6:51
13

Logging in Inside the Test

6:57
14

Resetting the Database Between Tests

4:51
15

Base Test Class full of Goodies

8:30
16

ACL: Only Owners can PUT a CheeseListing

9:23
17

ACL & previousObject

8:04
18

Access Control & Voters

8:25
19

Adding the plainPassword Field

7:31
20

Data Persister: Encoding the Plain Password

8:03
21

Validation Groups

5:44
22

Conditional Field Setup

6:42
23

Testing, Updating Roles & Refreshing Data

9:22
24

Context Builder & Service Decoration

6:50
25

Context Builder: Dynamic Fields/Groups

7:47
26

Automatic Serialization Groups

5:59
27

Resource Metadata Factory: Dynamic ApiResource Options

8:45
28

Dynamic Groups without Caching

10:34
29

Custom Normalizer: Object-by-Object Dynamic Fields

9:30
30

Diving into the Normalizer Internals

4:49
31

A "Normalizer Aware" Normalizer

6:49
32

Normalizer & Completely Custom Fields

7:32
33

Locking down the CheeseListing.owner Field

8:16
34

Custom Validator

5:40
35

Security Logic in the Validator

6:46
36

Auto-set the Owner: Entity Listener

9:46
37

Query Extension: Auto-Filter a Collection

9:37
38

Automatic 404 on Unpublished Items

5:26
39

Filtering Related Collections

10:50

This tutorial has a new version, check it out!

> Symfony 5 > API Platform 2 Part 2: Security

Buy Access to Course

28.

Dynamic Groups without Caching

|

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

6 Comments

Sort By

Login or Register to join the conversation

Carlos 5 years ago edited

Hi!!! I'm trying to find out how to pluralize the words to our native language, Portuguese. It seems to be related to the class in doctrine/inflector/lib/Doctrine/Inflector/InflectorFactory.php. But it is hardcoded there:

`public static function create() : LanguageInflectorFactory

{
    return self::createForLanguage(Language::ENGLISH);
}`

If I change that to self::createForLanguage(Language::PORTUGUESE) it works. I think that it should be configurable.

Thanks

1 |

Victor SFCASTS Carlos 5 years ago

Hey Carlos,

Yes, I think you need to call that "createForLanguage()" method directly and pass the language you want. That method is also public, so you can call it on that object. The "create()" method is really hardcoded to the English version.

Cheers!

1 |

Carlos Victor 5 years ago

Hey Victor, thank you! But where could I call this method? Because in anywhere I'm calling the create() method. It's part of the configuration. I couldn't find in the Api Platform docs where to change this. I searched too in the Doctrine and Symfony docs, but actually, in the Symfony docs it says that now the Inflector Component is deprecated (https://symfony.com/doc/cur.... Maybe there's a way to configure through yaml, or maybe through decoration?

|

weaverryan SFCASTS Carlos 5 years ago edited

Hey Carlos!

Happy new year!

Yea, I see the issue. First, it's not the Symfony inflector we're dealing with - but the Doctrine one... not that this helps us really (just noting that for clarity). Inside API Platform, I don't see any hook points: they call the Inflector statically in a few places.

But, don't despair! Even though we can't override/configure this InflectorFactory directly, we CAN configure/control the things that use it. And actually, I only the pluralize method used in 2 places:

A) RouteNameGenerator
B) DashPathSegmentNameGenerator and UnderscorePathSegmentNameGenerator (the 2nd is the default, iirc)

My guess is that what you want is to control how the URLs are generated (e.g. Product class -> /api/products) is that correct? If so, then you want to override the "path name segment generator". We talk about that (kinda) here: https://symfonycasts.com/screencast/api-platform-extending/custom-resource#codeblock-0afd22e71b

What I would do is:

Create a class that implements PathSegmentNameGeneratorInterface and decorates the api_platform.path_segment_name_generator.dash service. Then, configure YOUR new service under the api_platform. path_segment_name_generator config.

Let me know if that helps!

Cheers!

1 |

Carlos weaverryan 5 years ago

Hey Ryan, thanks again. Actually the only problem is if I choose to go with the plurals in the resources. I think that I will set the "path" inside each Entity and stick with the singular words. Can you tell me your opinion, would I lose something doing that?

|

weaverryan SFCASTS Carlos 5 years ago edited

Hey Carlos!

I don't see any issue with being explicit and putting the "path" inside each entity - just more work for you (and, of course, you should be careful to be consistent of course!) but always a solid thing to do :).

Cheers!

1 |

This tutorial works great for Symfony 5 and API Platform 2.5/2.6.

Symfony 4 API Platform 2.4

What PHP libraries does this tutorial use?

// composer.json
{
    "require": {
        "php": "^7.1.3, <8.0",
        "ext-ctype": "*",
        "ext-iconv": "*",
        "api-platform/core": "^2.1", // v2.4.5
        "composer/package-versions-deprecated": "^1.11", // 1.11.99
        "doctrine/annotations": "^1.0", // 1.13.2
        "doctrine/doctrine-bundle": "^1.6", // 1.11.2
        "doctrine/doctrine-migrations-bundle": "^2.0", // v2.0.0
        "doctrine/orm": "^2.4.5", // v2.7.2
        "nelmio/cors-bundle": "^1.5", // 1.5.6
        "nesbot/carbon": "^2.17", // 2.21.3
        "phpdocumentor/reflection-docblock": "^3.0 || ^4.0", // 4.3.1
        "symfony/asset": "4.3.*", // v4.3.2
        "symfony/console": "4.3.*", // v4.3.2
        "symfony/dotenv": "4.3.*", // v4.3.2
        "symfony/expression-language": "4.3.*", // v4.3.2
        "symfony/flex": "^1.1", // v1.21.6
        "symfony/framework-bundle": "4.3.*", // v4.3.2
        "symfony/http-client": "4.3.*", // v4.3.3
        "symfony/monolog-bundle": "^3.4", // v3.4.0
        "symfony/security-bundle": "4.3.*", // v4.3.2
        "symfony/twig-bundle": "4.3.*", // v4.3.2
        "symfony/validator": "4.3.*", // v4.3.2
        "symfony/webpack-encore-bundle": "^1.6", // v1.6.2
        "symfony/yaml": "4.3.*" // v4.3.2
    },
    "require-dev": {
        "hautelook/alice-bundle": "^2.5", // 2.7.3
        "symfony/browser-kit": "4.3.*", // v4.3.3
        "symfony/css-selector": "4.3.*", // v4.3.3
        "symfony/maker-bundle": "^1.11", // v1.12.0
        "symfony/phpunit-bridge": "^4.3", // v4.3.3
        "symfony/stopwatch": "4.3.*", // v4.3.2
        "symfony/web-profiler-bundle": "4.3.*" // v4.3.2
    }
}

Previous Chapter

Next Chapter