Skip to content

Create HttpFoundation\Request->toObject() Function #46865

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

Closed
wants to merge 6 commits into from
Closed

Create HttpFoundation\Request->toObject() Function #46865

wants to merge 6 commits into from

Conversation

TheDevick
Copy link

@TheDevick TheDevick commented Jul 5, 2022

Q A
Branch? 6.2
Bug fix? no
New feature? yes
Deprecations? no
Tickets Feat #46864
License MIT
Doc PR symfony/symfony-docs#16941

@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 6.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

Copy link

@FabienPapet FabienPapet left a comment

Choose a reason for hiding this comment

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

I think return (object) $this->toArray() is the way to go as the try catch is not useful

@TheDevick
Copy link
Author

I think return (object) $this->toArray() is the way to go as the try catch is not useful

So you mean remove the try and catch from the code?

@FabienPapet
Copy link

Yes, I think that you don't need to catch the exception from the toArray()

Copy link
Contributor

@ro0NL ro0NL left a comment

Choose a reason for hiding this comment

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

i'd prefer casting in userland (as always :))

@fabpot
Copy link
Member

fabpot commented Jul 6, 2022

I agree that there is no need for this method to be part of core as the use case is very specific and not broad enough. Thank you for proposing.

@fabpot fabpot closed this Jul 6, 2022
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.

5 participants