8000 [Form] Make exception handling consistent with other components by Olden · Pull Request #7706 · symfony/symfony · GitHub
[go: up one dir, main page]

Skip to content

[Form] Make exception handling consistent with other components #7706

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

Merged
merged 1 commit into from
Apr 20, 2013

Conversation

Olden
Copy link
@Olden Olden commented Apr 18, 2013
Q A
Bug fix? no
New feature? no
BC breaks? no
Deprecations? no
Tests pass? yes
Fixed tickets #6544
License MIT

@Olden
Copy link
Author
Olden commented Apr 18, 2013

ping @bschussek

@webmozart
Copy link
Contributor

Hi @Olden, thank you for this much needed PR! :) Unfortunately there are a few other PRs in the merge queue that create a few conflicts with yours. Would you mind to rebase your PR on symfony/master once #6522 and #6573 are merged?

@Olden
Copy link
Author
Olden commented Apr 18, 2013

@bschussek no problem, I'll wait.

@canni
Copy link
Contributor
canni commented Apr 19, 2013

IMO renaming/removing even things like exceptions IS a BC-Break and should be mentioned in changelog/update documents.

@fabpot
8000 Copy link
Member
fabpot commented Apr 19, 2013

Both PRs referenced by @bschussek have been merged now. And Yes, this is a BC break.

@webmozart
Copy link
Contributor

I think it is not necessary to rename any exception. Otherwise this PR should be fine in terms of BC.

@Olden
Copy link
Author
Olden commented Apr 19, 2013

A bit later today I'll make rebase and update changelog file.

@webmozart
Copy link
Contributor

Thank you! I would appreciate if you could check the full component code again for "old-style" exceptions, because a couple of older PRs were merged recently. Their exception code possibly needs to be adapted too.

@Olden
Copy link
Author
Olden commented Apr 19, 2013

Rebased. @bschussek plz review this.

@Olden Olden closed this Apr 19, 2013
@Olden Olden reopened this Apr 19, 2013
@Olden
Copy link
Author
Olden commented Apr 19, 2013

Sorry for closing

@@ -27,7 +27,7 @@
*
* @return FormInterface The form named after the type
*
* @throws Exception\FormException if any given option is not applicable to the given type
* @throws \Symfony\Component\OptionsResolver\Exception\\InvalidOptionsException if any given option is not applicable to the given type
Copy link
Contributor

Choose a reason for hiding this comment

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

one \ too much

@webmozart
Copy link
Contributor

Apart from my comments, this PR looks very good! Thank you! :)

@webmozart
Copy link
Contributor

For everybody confused by the diff view, the "renamed" exceptions are really just removed (because unused) exceptions and new exceptions that Git wrongly considers "renamed".

@Olden
Copy link
Author
Olden commented Apr 19, 2013

updated.

@Olden
Copy link
Author
Olden commented Apr 19, 2013

@bschussek not at all. It's pleasure to me to be a part of great community :)

8000

@webmozart
Copy link
Contributor

Could you please squash the commits into a single commit?

@Olden
Copy link
Author
Olden commented Apr 19, 2013

done

fabpot added a commit that referenced this pull request Apr 20, 2013
This PR was merged into the master branch.

Discussion
----------

[Form] Make exception handling consistent with other components

| Q             | A
| ------------- | ---
| Bug fix?      | no
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets | #6544
| License       | MIT

Commits
-------

bf9382e [Form] Make exception handling consistent with other components
@fabpot fabpot merged commit bf9382e into symfony:master Apr 20, 2013
@Olden Olden deleted the issue_6544 branch April 20, 2013 07:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants
0