Normalizer & Completely Custom Fields

Hey Patrick D.!

I'm not sure - we have several tutorials in front of it. So while it *is* tentatively on the schedule, it's likely will *not* be released earlier than 6 weeks from now. Sorry I can't give you better news!

Cheers!

Hey Zarloon,

Thank you for your interest in SymfonyCasts tutorials! Unfortunately, no plans to cover this topic fairly speaking, but I'll add it to our idea pool! JWT is more complex, but also a more powerful. If you're looking for something simpler - year, probably session-based thing would be easier. Well, maybe I can give you some tips about it and maybe they help you :) So, if we're talking about non-SPA page - it's easy, you just need to set true or false value on a property base on whether there's a current logged-in user or no. You can do it in twig template for example, if there's a "app.user" - set authorized to true, otherwise - set to false. And then, in your JS you just read that property and execute specific logic according to its value. But if you're talking about SPA - it's a bit more complex, not sure about the best approach there, probably JWT is something you need.

Btw, we cover JWT in a few screencasts, you can leverage our search to find related courses/videos: https://symfonycasts.com/se... - I hope that would help you.

Cheers!

Hey Stephane!

Hmmm. I'm not sure what the problem is, however, you may have given me a hint:

I noticed that when I launch a request on get/api/users, I have all the informations of each user except those of the connected user

You mentioned "I have all the informations of each user". Do you really see ALL of the fields for those other users? If so, it makes me think that you, by default, are serializing the user with NO serialization groups. And so, it's showing all of the fields. Then, when you are the "connected user", you are then adding a single group - owner:read. So suddenly, you are only serializing things in that ONE group.

So I would back up and make sure that, in your normal situation, you are serializing using the user:read group.

Let me know if that helps!

Cheers!

Hey @Ryan,

Thank for your answer.

Yes I see all fields (no phone) for other users ?

I think I find the problem : I add [] on line $context['groups'][] = 'owner:read'; in normalize method of UserNormalizer class.

But now when I run tests, there is an error :
1) App\Tests\Functional\UserResourceTest::testGetUser
Error: [] operator not supported for strings

probably a type error of a property in the User class ?

Hey Stephane!

Hmm. Yes, that was a good fix. Now, about the error:

Error: [] operator not supported for strings

It tells me that $context['groups'] is set to a string currently instead of an array. Technically speaking, the serializer works fine if you set the serialization groups to a string - it just turns that into an array that contains that one group internally. But the question in this case is: why is it a string? In my User class, I have:

normalizationContext={"groups"={"user:read"}},

So, groups is set to an array with user:read inside. But in your case, it's a string. So you have 2 options:

1) Try to figure out why your groups are a string and not an array and fix it to be an array.
2) Code around this in UserNormalizer:

// if it's a string, turn it into an array
if (is_string($context['groups'])) {
    $context['groups'] = [$context['groups']];
}
$context['groups'][] = 'owner:read';

Let me know if that helps!

Cheers!

Hello Ryan,

Thank for your answer. I fix the type problem with your test proposition. All tests pass.

Cheers.