Skip to content

Fixes the stack traces of the deprecation logs #16658

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
Nov 25, 2015

Conversation

javiereguiluz
Copy link
Member

Q A
Bug fix? yes
New feature? no
BC breaks? no
Deprecations? no
Tests pass? yes
Fixed tickets #16640
License MIT
Doc PR

The stack trace information was displayed in a very confusing way. Now it's easier to understand what is called from which file and line.

Before

stack_trace_before

After

stack_trace_after

@Tobion
Copy link
Contributor

Tobion commented Nov 25, 2015

👍 Nice

Status: Reviewed

@stof
Copy link
Member

stof commented Nov 25, 2015

👍

@Tobion
Copy link
Contributor

Tobion commented Nov 25, 2015

Thank you Javier.

@Tobion Tobion merged commit 09f4895 into symfony:2.8 Nov 25, 2015
Tobion added a commit that referenced this pull request Nov 25, 2015
…uiluz)

This PR was merged into the 2.8 branch.

Discussion
----------

Fixes the stack traces of the deprecation logs

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

The stack trace information was displayed in a very confusing way. Now it's easier to understand what is called from which file and line.

### Before

![stack_trace_before](https://cloud.githubusercontent.com/assets/73419/11392640/5c02607a-935b-11e5-8f99-812fbd97aad3.png)

### After

![stack_trace_after](https://cloud.githubusercontent.com/assets/73419/11392650/5f0b821a-935b-11e5-8472-7fae9bd21149.png)

Commits
-------

09f4895 Fixes the stack traces of the deprecation logs
@apfelbox
Copy link
Contributor

@javiereguiluz would it make sense to wrap all inline code fragments with <code>...</code>? (not just on this page, but every other page, too?)

@javiereguiluz
Copy link
Member Author

@apfelbox it would probably be "better" ... but at the same time very boring to do. Since the profiler is something internal and for developers only, we can skip some "correctness".

@apfelbox
Copy link
Contributor

@javiereguiluz I didn't mean from a semantic point of view but by using a monospaced font for inline <code>.
I think it would improve the legibility of the profiler quite a lot by establishing the rule "Code = monospaced font".

@apfelbox
Copy link
Contributor

(I mean for the stack trace, I know that we can't do that for the deprecation message itself…)

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
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy