Chapters

27 Chapters | 2:54:11 |

01

¡Instalación de la plataforma API!

6:42
02

Nuestro primer ApiRecurso

5:37
03

Swagger: Documentación de API instantánea e interactiva

8:32
04

Especificación OpenAPI

6:32
05

JSON-LD: Contexto para tus datos

10:30
06

Hydra: Describiendo las clases de la API, las operaciones y más

6:01
07

Depuración de la API con el Perfilador

3:17
08

Operaciones

5:21
09

El serializador

9:13
10

Grupos de serialización

9:34
11

@NombreSerializado y Args del Constructor

7:15
12

Filtrar y buscar

6:02
13

Filtro de propiedades: Conjuntos de campos dispersos

5:34
14

Paginación

4:34
15

Más formatos: HAL Y CSV

6:05
16

Validación

6:29
17

Creación de la entidad de usuario

5:07
18

Recurso API de usuario

7:20
19

Recursos relacionados

7:38
20

Relaciones e IRIs

4:39
21

Relación incrustada

7:54
22

Escritura incrustada

8:22
23

Añadir elementos a una propiedad de la colección

4:38
24

Crear objetos incrustados

7:06
25

Eliminar elementos de una colección

5:29
26

Filtrar en las relaciones

5:06
27

Subrecursos

3:36

This tutorial has a new version, check it out!

> Symfony 5 > Plataforma API: APIs RESTful serias

Buy Access to Course

17.

Creación de la entidad de usuario

|

|

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

20 Comments

Sort By

Login or Register to join the conversation

Steven L. 6 years ago edited

If you're running mariadb and getting the error "SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max key length is 767 bytes" when running the migration, edit User.php and limit the username length to 191:
` /**

 * @ORM\Column(type="string", length=191, unique=true)
 */
private $username;`

1 |

Victor SFCASTS Steven L. 6 years ago

Hey Steve,

Thanks for this tip!

Cheers!

|

Jonas 3 years ago

Using the latest Symfony binary and following along the tutorial for API Platform (which is still based on Symfony 4/5), I get the following error:

>bin/console make:entitiy   

In SecurityExtension.php line 307:
                                                                       
  Invalid firewall "main": user provider "users_in_memory" not found.

It seems that the command bin/console make:user replaces

    providers:
        users_in_memory: { memory: null }

with

    providers:
        # used to reload user from session & other features (e.g. switch_user)
        app_user_provider:
            entity:
                class: App\Entity\User
                property: email

but leaves

    firewalls:
        dev:
            pattern: ^/(_(profiler|wdt)|css|images|js)/
            security: false
        main:
            anonymous: true
            provider: users_in_memory

intact. We no longer have a users_in_memory provider, which leads to the error.

The make:user command should probably result in a coherent state of the security.yaml file, so either users_in_memory or app_user_provider, not a mix of both.

TL:DR:

Replace provider: users_in_memory with provider: app_user_provider in security.yaml under security:firewalls:main

I hope this does not cause problems down the road, but so far everything worked as expected.

|

weaverryan SFCASTS Jonas 3 years ago

Hi Jonas!

Thanks for posting this! It seems like a bug in MakerBundle - it's possible it's still a bug, or it may have been fixed (I work on MakerBundle, but we do so much that I can't remember when we do things 🙃). Anyways - thanks for posting - and if you ARE using the latest version of MakerBundle, it would be awesome if you could open an issue about this on https://github.com/symfony/maker-bundle

Cheers!

|

Jonas weaverryan 3 years ago

Hi Ryan, thanks for the quick answer!

My maker bundle version is not current, as I followed the advice in chapter 2 and installed version 1.11.

So maybe it is fixed, just not if you're following along with the course. :)

All the best,

Jonas

|

André P. 5 years ago edited

If you're using Symfony 5.3, you'll get the following error when trying to add new fields to the User entity:

PHP Fatal error: Class App\Entity\User contains 1 abstract method and must therefore be declared abstract or implement the remaining methods (Symfony\Component\Security\Core\User\UserInterface::getUsername) in /mnt/c/laragon/www/api-platform/src/Entity/User.php on line 13

This is because the method getUsername was deprecated in favor of getUserIdentifier, but the UserInterface still implements the old method, not the new one.

You can find more information here: <a href="https://github.com/symfony/symfony/pull/41493">https://github.com/symfony/symfony/pull/41493</a>.

Just add the following code and then try again:
`
/**

 * @deprecated in Symfony 5.3
 */
public function getUsername(): string
{
 return $this->getUserIdentifier();
}

`

|

Victor SFCASTS André P. 5 years ago

Hey Andre,

Thank you for sharing the solution with others! Looks like you also need to implement that 1 abstract method as well as I can see from the error message. I think we will add a note about it, thanks!

Cheers!

|

weaverryan SFCASTS Victor 5 years ago

Yep, this is my bad. Well, once 5.3.1 came out, we needed to merge and tag this PR- https://github.com/symfony/...

That's my job - I've been really busy, but it will happen soon!

Cheers!

|

Mohammed 5 years ago

Hello!

I'm using MongoDB instead of MySQL and I figured I couldn't use the make command to create a Document.
But I wanted to use the Symfony built-in authentication mechanism with json_login.

Is it possible for it to work by simply replacing Entity with Document in the app_user_provider?
Thanks!

|

weaverryan SFCASTS Mohammed 5 years ago

Hey @Med!

Yep! Symfony's security system doesn't care if your User object is loaded via Doctrine ORM, Doctrine ODM or via an alien spaceship ;). So that's good. However, I don't believe that the ODM integrates *that* well - you can't just change the config. But, it's still pretty easy:

1) Create a class called UserProvider and make it implement UserProviderInterface
2) Fill in the methods - loadUserByUsername() is the key method that json_login will call
3) Pass your service id (well, class name) to the "providers" config in security.yaml

My answer is a big vague, because the docs are here! https://symfony.com/doc/cur...

Let me know if that helps!

Cheers!

|

sadikoff 6 years ago edited

Hi there

Could you please share your mysql(mariadb) server version?

Cheers!

|

hanen sadikoff 6 years ago

10.1.3 mariaDB
The JSON alias was added in maria DB 10.2.7 so I have to upgrade mariaDB? is that correct

|

sadikoff hanen 6 years ago edited

in this case you have 2 options.
First is to upgrade your server
Second is more interesting you can try configure doctrine.dbal.server_version to correspond you server version
Example:


doctrine:
    dbal:
        server_version: 'mariadb-10.1.3'

Hope it will help you, Cheers!

|

hanen sadikoff 6 years ago

I choose the second option and I changed the server version but I got the following error: SQLSTATE[HY000] [1045] Access denied for user 'root'@'localhost' (using password: NO)
I added a password in .env file DATABASE_URL=mysql://root:0000@127.0.0.1:3306/Glabre.
An exception occurred in driver: SQLSTATE[HY000] [1045] Access denied for user 'root'@'localhost' (using password: YES)

1 |

sadikoff hanen 6 years ago edited

Hey hanen

Oh I'm so sorry for late message, I missed your comment at all =(
I hope you you solved this issue, because honestly I have no Idea why this error occurred, Probably it was some user password misconfiguration

Cheers!

1 |

hanen sadikoff 6 years ago

I finally fixed it ;)

|

sadikoff hanen 6 years ago

Great! If it's not a secret, what was the solution?

|

hanen sadikoff 6 years ago

upgrading mariadb from 10.1 to 10.2.x & of course setup a new MySQL root user password by default run as administrator :))))

|

sadikoff hanen 6 years ago

Awesome! Sounds like an easy fix =)

Cheers!

|

hanen sadikoff 6 years ago

;))
Serveur : 127.0.0.1 via TCP/IP
Type de serveur : MariaDB
Connexion au serveur : SSL n'est pas utilisé Documentation
Version du serveur : 10.2.9-MariaDB - mariadb.org binary distribution
Version du protocole : 10
Utilisateur : root@localhost

|

Este tutorial funciona muy bien para Symfony 5 y la Plataforma API 2.5/2.6.

Symfony 4 API Platform 2.4

What PHP libraries does this tutorial use?

// composer.json
{
    "require": {
        "php": "^7.1.3",
        "ext-ctype": "*",
        "ext-iconv": "*",
        "api-platform/core": "^2.1", // v2.4.3
        "composer/package-versions-deprecated": "^1.11", // 1.11.99
        "doctrine/annotations": "^1.0", // 1.10.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.5
        "nesbot/carbon": "^2.17", // 2.19.2
        "phpdocumentor/reflection-docblock": "^3.0 || ^4.0", // 4.3.1
        "symfony/asset": "4.2.*|4.3.*|4.4.*", // v4.3.11
        "symfony/console": "4.2.*", // v4.2.12
        "symfony/dotenv": "4.2.*", // v4.2.12
        "symfony/expression-language": "4.2.*|4.3.*|4.4.*", // v4.3.11
        "symfony/flex": "^1.1", // v1.21.6
        "symfony/framework-bundle": "4.2.*", // v4.2.12
        "symfony/security-bundle": "4.2.*|4.3.*", // v4.3.3
        "symfony/twig-bundle": "4.2.*|4.3.*", // v4.2.12
        "symfony/validator": "4.2.*|4.3.*", // v4.3.11
        "symfony/yaml": "4.2.*" // v4.2.12
    },
    "require-dev": {
        "symfony/maker-bundle": "^1.11", // v1.11.6
        "symfony/stopwatch": "4.2.*|4.3.*", // v4.2.9
        "symfony/web-profiler-bundle": "4.2.*|4.3.*" // v4.2.9
    }
}

Previous Chapter

Next Chapter