Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

[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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
daniser wants to merge23 commits intosymfony:7.4
base:7.4
Choose a base branch
Loading
fromdaniser:serialized-names-and-paths-per-group

Conversation

daniser
Copy link

@daniserdaniser commentedSep 11, 2024
edited
Loading

QA
Branch?7.2
Bug fix?no
New feature?yes
Deprecations?no
IssuesFix#30483,#53858
LicenseMIT

At the moment some of my ownMetadataAwareNameConverter 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!

cyril-barragan and valtzu reacted with thumbs up emoji
@carsonbot
Copy link

Hey!

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

Symfony has acontribution guide which I suggest you to read.

In short:

  • Always add tests
  • Keep backward compatibility (seehttps://symfony.com/bc).
  • Bug fixes must be submitted against the lowest maintained branch where they apply (seehttps://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
publicfunction __construct(string$serializedPath,string|array$groups = [])
publicfunction __construct(string$serializedPath,string|array$groups = ['*'])

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

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

@OskarStarkOskarStark 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 forSerializedName)

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 tono groups".
As alternative to fallback to['*'], we can throw exception. WDYT?

Sergey Danilchenko added4 commitsNovember 5, 2024 12:33
Sergey Danilchenko added3 commitsNovember 11, 2024 11:10
@fabpotfabpot modified the milestones:7.2,7.3Nov 20, 2024
@fabpotfabpot modified the milestones:7.3,7.4May 26, 2025
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@OskarStarkOskarStarkOskarStark left review comments

@mtarldmtarldmtarld left review comments

@dunglasdunglasAwaiting requested review from dunglasdunglas is a code owner

Assignees
No one assigned
Projects
None yet
Milestone
7.4
Development

Successfully merging this pull request may close these issues.

[Serializer] SerializedName based on groups
5 participants
@daniser@carsonbot@OskarStark@mtarld@fabpot

[8]ページ先頭

©2009-2025 Movatter.jp