8000 [WIP] [TwigBundle] [Exception] Make return value similar to error.json.twig by clemens-tolboom · Pull Request #11078 · symfony/symfony · GitHub
[go: up one dir, main page]

Skip to content

[WIP] [TwigBundle] [Exception] Make return value similar to error.json.twig #11078

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

Conversation

clemens-tolboom
Copy link
Contributor
Q A
Bug fix? I guess this is a bug
New feature? The exception structure changes for the default
BC breaks? The exception structure changes for the default
Deprecations? [yes
Tests pass? [yes
Fixed tickets
License MIT
Doc PR

The result for error.json.twig and exception.json.twig differ making the client forced to check for it's result.

We think the structure should be the same to make the ie a javascript client try to respond similar for --env=dev|prod

@clemens-tolboom
Copy link
Contributor Author

Running tests just for this bundle depends on #11077

@clemens-tolboom
Copy link
Contributor Author

I have no clues why both Travis and fabbot.io failed.

@cordoval
Copy link
Contributor
cordoval commented Jun 8, 2014

@clemens-tolboom is not your fault on travis-ci, about fabbot.io no idea

@fabpot
Copy link
Member
fabpot commented Jul 23, 2014

👍

@fabpot
Copy link
Member
fabpot commented Aug 28, 2014

ping @symfony/deciders

@lsmith77
Copy link
Contributor

I guess due to the different structure anyone relying on the structure probably just created code that would be able to deal with both structures .. at the very least it should be an easy fix to either remove the now no longer needed version or to overwrite this template.

so +1

@romainneutron
Copy link
Contributor

👍 however: should we add a note in the CHANGELOG.md or UPGRADE.md files ?

@stof
Copy link
Member
stof commented Aug 28, 2014

I think the changelog is enough (this does not affect the prod environment, only the debug ones)

@stof
Copy link
Member
stof commented Aug 28, 2014

👍

@fabpot
Copy link
Member
fabpot commented Sep 1, 2014

@clemens-tolboom Can you add a note in the CHANGELOG file of the bundle?

@clemens-tolboom clemens-tolboom force-pushed the feature/better-json-exception branch from 3903d81 to 8674e5a Compare September 3, 2014 12:56
@@ -1,6 +1,11 @@
CHANGELOG
=========

2.4.0
Copy link
Member

Choose a reason for hiding this comment

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

It's going to be in 2.6 and this is a BC break, so you should prefix the line with [BC BREAK] (as such, I would also change fixed by changed.)

@fabpot
Copy link
Member
fabpot commented Sep 22, 2014

Thank you @clemens-tolboom.

@fabpot fabpot closed this Sep 22, 2014
fabpot added a commit that referenced this pull request Sep 22, 2014
…ar to error.json.twig (clemens-tolboom)

This PR was squashed before being merged into the 2.6-dev branch (closes #11078).

Discussion
----------

[WIP] [TwigBundle] [Exception] Make return value similar to error.json.twig

| Q             | A
| ------------- | ---
| Bug fix?      | I guess this is a bug
| New feature?  | The exception structure changes for the default
| BC breaks?    | The exception structure changes for the default
| Deprecations? | [yes|no]
| Tests pass?   | [yes|no]
| Fixed tickets |
| License       | MIT
| Doc PR        |

The result for `error.json.twig` and `exception.json.twig` differ making the client forced to check for it's result.

We think the structure should be the same to make the ie a javascript client try to respond similar for --env=dev|prod

Commits
-------

4a59f98 [WIP] [TwigBundle] [Exception] Make return value similar to error.json.twig
@clemens-tolboom clemens-tolboom deleted the feature/better-json-exception branch September 23, 2014 16:48
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.

6 participants
0