Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
[DX] [TwigBundle] Enhance the new exception page design#22439
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
Uh oh!
There was an error while loading.Please reload this page.
Conversation
sustmi commentedApr 14, 2017 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Wait, I found that the problem with wrapping long lines shown here:#20951 (comment) still happens. |
sustmi commentedApr 14, 2017 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Wrapping is fixed in the new commit. |
robfrawley commentedApr 14, 2017
Personally, I preferred the less dense "double line" of the original. |
sustmi commentedApr 14, 2017 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
@robfrawley, do you think that with single line spacing the code is harder to read? |
curry684 commentedApr 14, 2017 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
👎 on that one as it then dominates the average developer's screen completely. And you can just middle/right click the filename above the snippet to see the full scrollable context if you really need it. Totally down with bringing the line spacing down though, just tried it and yes it reads more like actual code. And it does give room to increase the context to 5 without sacrificing call stack. |
sustmi commentedApr 15, 2017 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
7c794b0 toc2225c4Comparesustmi commentedApr 15, 2017
Rebased to the current master to rerun Travis CI. |
javiereguiluz commentedMay 31, 2017
I'm sorry I didn't review this on time for 3.3.0 ... I even thought this was merged! There are some things that I'm not sure about ... but others that I like. Tomorrow I'll add more details. Thanks! |
apfelbox commentedJun 1, 2017
stof commentedJun 1, 2017
@apfelbox IMO, this is overkill. You have access to the full file anyway if you want. |
stof commentedJun 1, 2017
@sustmi can you rebase this on top of the Symfony 3.4 branch to fix conflicts ? |
ogizanagi commentedJun 2, 2017 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
As I said in#22971 (comment), I'd love to see this merged in 3.3 as a bug fix rather than in 3.4. There is no DX nor feature to me, just UI/UX improvements and fixes for minor but annoying behavior issues. :) |
nicolas-grekas commentedJun 2, 2017
@sustmi would you mind rebasing please? |
curry684 commentedJun 2, 2017
I second the 3.3.1 vote. It's not a feature, just an improvement on 3.3-introduced behavior. DX/UX improvements have always been allowed in patch releases, no reason to postpone it. |
c2225c4 to6850170Comparesustmi commentedJun 4, 2017
I rebased the PR to 3.4 as@stof adviced. Is that all right? |
It was necessary to remove table layout and replace it with DIVs and SPANsbecause it was messing with width calculations.
6850170 to0173d22Comparesustmi commentedJun 4, 2017
I just noticed the discussion in#22971 (comment) so I guess you actually wanted me to rebase it to 3.3. |
fabpot commentedJun 4, 2017
You also need to change the target to 3.3. |
sustmi commentedJun 4, 2017
Oh, thanks for the notice. Done. |
fabpot commentedJun 9, 2017
@javiereguiluz Is it ready to merge or do you need more time to review? |
javiereguiluz left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
fabpot commentedJul 6, 2017
Thank you@sustmi. |
…ustmi)This PR was squashed before being merged into the 3.3 branch (closes#22439).Discussion----------[DX] [TwigBundle] Enhance the new exception page design| Q | A| ------------- | ---| Branch? | 3.3| Bug fix? | no| New feature? | no| BC breaks? | no| Deprecations? | no| Tests pass? | yes| Fixed tickets | -| License | MIT| Doc PR | -- [x] Fix the problem with wrapping wide lines (#20951 (comment))I got motivated by recent PR#20951 and redesigned the exception page even more.Compare before: with after: (Ignore the the "sf" toolbar icon in the middle of the page. This is how Firefox does full-page screenshots.)The most noticeable changes:- removed double line spacing (it just does not feel natural)- file context increased from 3 to 10 lines (it helps me to better orientate in the code)- added horizontal scrollbar for the cases when the code is wider- the highlighted line color is more saturated in order to be noticed easilyCommits-------43212b9 [DX] [TwigBundle] Enhance the new exception page design




Uh oh!
There was an error while loading.Please reload this page.
I got motivated by recent PR#20951 and redesigned the exception page even more.
Compare before:

with after:
(Ignore the the "sf" toolbar icon in the middle of the page. This is how Firefox does full-page screenshots.)
The most noticeable changes: