Crear tu primer ApiResource

Hey Szymon!

I know this error! If you're using the code from the course, then we're using Postgres. The error means that you need to install the pgsql php extension - e.g. like described here (the exact setup instructions will depend on your operating system): https://stackoverflow.com/questions/10085039/postgresql-pdoexception-with-message-could-not-find-driver#answer-48858539

Or, if you'd rather use Mysql, you can skip the migrations and run doctrine:schema:update --force instead (after configuring your app to talk to your mysql database).

Let me know if this helps!

Cheers!

yeah, that's right. I am using Windows, and I just removed semicolon in xampp/php/php.ini

extension=pdo_pgsql
...
extension=pgsql

and it's running good.

But it's kind weird for me, because I am not using XAMPP, I installed php directly in my computer, but most important is that working anyway :)

additional query: what is the difference between using MySQL and PostgreSQL in this tutorial? I remember in Symfony5 tutorial we used MySQL.
Is chance to see this database tables in friendly environemnt like phpMyAdmin or something similar? does it require a more difficult setup?

Hey Szymon,

In this tutorial, the only difference you'll find if you use MySQL instead of PostgreSQL is the migration files. The queries generated by Doctrine will be specific to MySQL, but besides that, nothing else will be different.

Is chance to see this database tables in friendly environemnt like phpMyAdmin or something similar? does it require a more difficult setup?

I found this tool for Postgres. However, I don't know how hard it might be to set it up. https://github.com/phppgadmin/phppgadmin

Cheers!

OK - I found the answer. At least to remove the camelCase fields.

https://api-platform.com/docs/core/serialization/#name-conversion-for-symfony

# api/config/services.yaml
services:
    'Symfony\Component\Serializer\NameConverter\CamelCaseToSnakeCaseNameConverter': ~

# api/config/packages/api_platform.yaml
api_platform:
  name_converter: 'Symfony\Component\Serializer\NameConverter\CamelCaseToSnakeCaseNameConverter'

I did try the reverse SnakeCaseToCamelCaseNameConverter and it worked as expected.

But it turns out that using #[Groups...] will prevent the duplication of the fields as well. Then using [#SerializedName...] can adjust the name to whatever is preferred. No need for the explicit Name Converters.

That said, the Name Converters only required editing two config files and would apply to all API Resources. Using the Groups and SerializedName as to be applied to every field - a lot more work.

Of course, I believe all of this could be handled very simply by using DTOs instead of Doctrine Entities. I just haven't gotten that far following this tutorial.

Yes, DTOs would help you in that situation, although DTOs add their own complexity :)

Hey Jeff,

Good job found the answer yourself! And thanks for sharing this solution with others

Cheers!

Hey @David-L

Sorry for the slow reply. How are you starting up the web server? Remember that you need to do it through the Symfony CLI so it can set up docker automatically symfony serve -d

Cheers!

I'm not even getting to the point of running the web server, just running symfony console doctrine:migrations:status results in the error message after a 60 second time out. I ended up using mysql for my database instead.

I think there's an issue with your DB authentication, for some reason you're using GSSAPI. Try disabling it by appending this to your DB connection string ?gssencmode=disable

The connection string was generated by the Symfony CLI and stored in the DATABASE_URL env var, I was following the video and using the course files verbatim. Is there any other way to disable that so i can avoid explicitly defining the connection string?

I think you can do this: in your doctrine.yaml config file

doctrine:
    dbal:
        options:
            gssencmode: disable

Or, you could try changing the authentication mode directly in your docker-compose.yml file:

services:
    database:
        environment:
            POSTGRES_HOST_AUTH_METHOD: md5

(I'm not 100% sure this latter option will work but you can give it a try)

Cheers!

I changed the "api-platform/core" version in the composer from 3.2.2 to 3.2.0, now the error is gone, https://127.0.0.1:8000/api is loading. But when I try to execute a get request, I still get the response:

Symfony Local Web Server: unable to fetch the response from the backend: unexpected EOF

Hey @Elena

That's unexpected, I believe there's something odd with your vendors, try re-installing them rm -r vendor/ and run composer install again. Oh, and restart the web server just in case

Cheers!

Hey @Eric-J!

Ah! That's not a friendly error :). From what I can tell... this looks like something weird and/or annoying :/. There are various solutions here - https://stackoverflow.com/questions/62807717/how-can-i-solve-postgresql-scram-authentication-problem - and none of them look great.

My advice: change the DATABASE_URL to use mysql or sqlite - something you're more familiar with. Then turn OFF the docker container and follow the tutorial. There's no need to get stopped by a silly detail like this. The tutorial will work 100% the same with pgsql, mysql or sqlite.

Cheers!

Hello,

Thanks for your help.

It seems that I had 2 Symfony local server running from 2 project at the same time and on the same database.

Anyhow, I got the error handled and could proceed on.

Kind regards

Good debugging Eric! The Docker container names are based on your directory name (not the full directory path, just the final name). So if you have 2 Symfony projects in directories named my_app, then they'll share the same containers... which isn't ideal :p. I hit this issue sometimes as well.

Cheers!

it was exhausting , but I found it:
api_platform.yml:

    mapping:
        paths:
            - '%kernel.project_dir%/src/Entity'
            - '%kernel.project_dir%/lib/SholGeneratr/Entity'

Hey Cameron,

I'm happy to hear you were able to find the solution yourself, well done! And thanks for sharing it with others

Cheers!

Hey @Ken

Yes, APIPlatform does not force you to create entities for your resources, you can do the exact same thing with data model classes
Here are the docs: https://api-platform.com/docs/core/dto/#using-data-transfer-objects-dtos

Cheers!

Hey @Yorane

I'm afraid I cannot help you with your Docker setup because I don't use it under WSL, but I have a question, does it only happens when you try to load the migrations?

Hi MolloKhan,

It's OK, I resolved my problem :)
Not only, every time my server try to connect to the container database.

To resolve the problem, we have to change the IP address in the .envfile with the container IP.

Oh cool, well done @Yorane
Tip: when you use Docker, you need to run any command through the Symfony CLI, so it can inject the correct env var values
symfony console app:foo

Cheers!

Thank's a lot dude!!!

My line is now like that and it works :D

DATABASE_URL="postgresql://app:!ChangeMe!@0.0.0.0:52327/app?serverVersion=15&charset=utf8"

Hey @Kev!

Well that's annoying! You're using Mysql, so the "could not find driver" is referring to the PHP pdo_mysql driver. Exactly HOW you install this depends on your system - e.g. with Ubuntu, it's often something like apt install php-mysql. Also, remember to restart your web server (e.g. the symfony binary) after installing the driver. And FINALLY. if you have multiple php binaries installed and you're not sure which one the symfony binary is using, you can always run symfony local:php:list to find out.

Cheers!

Hey @weaverryan ,

Thanks for your answer, the general idea is that i already have the php-mysql driver installed. I have it as a docker-compose procedure script for a container, AND i have it on my local ubuntu machine installed.

The default .env build with the default postrgres variable is the same result.

Weirdish issue really!

Cheers!

That IS weird. That usually means that some different, unexpected PHP binary is being used (that doesn't have the driver installed).... but these are a pain to figure out!