Skip to content

[Serializer] Support serialized names and paths configuration per group #58236

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 23 commits into
base: 7.4
Choose a base branch
from

Conversation

daniser
Copy link

@daniser daniser commented Sep 11, 2024

Q A
Branch? 7.2
Bug fix? no
New feature? yes
Deprecations? no
Issues Fix #30483, #53858
License MIT

At the moment some of my own MetadataAwareNameConverter tests are failing. I have tried to fix them, but everything I tried so far breaks existing tests. Just can't figure out what I have to do. Any help would be greatly appreciated!

@carsonbot
Copy link

Hey!

I see that this is your first PR. That is great! Welcome!

Symfony has a contribution guide which I suggest you to read.

In short:

  • Always add tests
  • Keep backward compatibility (see https://symfony.com/bc).
  • Bug fixes must be submitted against the lowest maintained branch where they apply (see https://symfony.com/releases)
  • Features and deprecations must be submitted against the 7.2 branch.

Review the GitHub status checks of your pull request and try to solve the reported issues. If some tests are failing, try to see if they are failing because of this change.

When two Symfony core team members approve this change, it will be merged and you will become an official Symfony contributor!
If this PR is merged in a lower version branch, it will be merged up to all maintained branches within a few days.

I am going to sit back now and wait for the reviews.

Cheers!

Carsonbot

*/
public function __construct(string $serializedPath)
public function __construct(string $serializedPath, string|array $groups = [])
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
public function __construct(string $serializedPath, string|array $groups = [])
public function __construct(string $serializedPath, string|array $groups = ['*'])

And then we can check that $groups is not empty
(same for SerializedName)

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What should we do in case $groups is empty? Throw exception or fall back to ['*']?
(BTW, I've implemented second option).

Copy link
Contributor

@OskarStark OskarStark left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Massive work in this PR, wow 👍 Thank you!

I added some comments

$groups = $line['groups'] ?? [];

if ($serializedName = $line['serialized_name'] ?? false) {
if (!\is_string($serializedName) || '' === $serializedName) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What about ' '?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you please elaborate? Do I need to trim string and then check for emptiness? Or just check for single space? What's the point?

{
try {
$this->serializedPath = new PropertyPath($serializedPath);
} catch (InvalidPropertyPathException $pathException) {
throw new InvalidArgumentException(\sprintf('Parameter given to "%s" must be a valid property path.', self::class));
}

$this->groups = ((array) $groups) ?: ['*'];
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure that we must fall back to ['*'] here, maybe an empty array can be valid in some cases (same for SerializedName)

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've tried that but it led to more failing tests. So I reverted it back until we decide what it could actually mean, so we could change the tests.
In my point of view, empty array here is nonsense, as it means "apply serialized name/path to no groups".
As alternative to fallback to ['*'], we can throw exception. WDYT?

Sergey Danilchenko added 4 commits November 5, 2024 12:33
# Conflicts:
#	src/Symfony/Component/Serializer/CHANGELOG.md
#	src/Symfony/Component/Serializer/Mapping/Loader/AttributeLoader.php
Sergey Danilchenko added 3 commits November 11, 2024 11:10
# Conflicts:
#	src/Symfony/Component/Serializer/NameConverter/MetadataAwareNameConverter.php
@fabpot fabpot modified the milestones: 7.2, 7.3 Nov 20, 2024
@fabpot fabpot modified the milestones: 7.3, 7.4 May 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Serializer] SerializedName based on groups
5 participants