Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
Fix error page preview tests#12540
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
Closed
Closed
Uh oh!
There was an error while loading.Please reload this page.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
…ption_controller (mpdude)This PR was submitted for the master branch but it was merged into the 2.6 branch instead (closes#12147).Discussion----------[TwigBundle] Fix error page preview for custom twig.exception_controller| Q | A| ------------- | ---| Bug fix? | yes| New feature? | no| BC breaks? | no| Deprecations? | no| Tests pass? | yes| Fixed tickets |#12147| License | MIT| Doc PR | n/aThe `testErrorPageAction()` always used the `showAction()` of TwigBundle's `ExceptionController`.You can, however, configure an alternate controller by setting `twig.exception_controller`.Thus, in order to get a proper preview, we need to forward to this configured controller (whichmay be the default one).This requires us to pass an additional parameter to `ExceptionController::showAction` to be able toget the *error* page even if configured otherwise in the constructor.(The other approach would have been to fiddle around with `ExceptionController`'s `debug` flag through a setter when going through the preview action, but that would have been even more messy.)Commits-------2065e00 [TwigBundle] Fix error page preview for custom twig.exception_controller
This adds an <abbr> element having a descriptive title thatdisplays the form element's type class name.
…(kix)This PR was submitted for the master branch but it was merged into the 2.6 branch instead (closes#12268).Discussion----------[DX] [Form] [WebProfiler] Added abbrs with type classes| Q | A| ------------- | ---| Bug fix? | no| New feature? | yes| BC breaks? | no| Deprecations? | no| Tests pass? | yes| Fixed tickets | none| License | MIT| Doc PR | noneThis adds an `<abbr/>` element having a descriptive title that displays the form element's type class name. Everyone wants to know what's the type behind a form child, yes?Looks like this:Commits-------0d20753 [DX] [Form] [WebProfiler] Added abbrs with type classes
ContributorAuthor
mpdude commentedNov 21, 2014
Dang, picked the wrong branch. Disregard. |
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See#12147 (comment) and following comments there.