8000 Document how to use xdebug.file_link_format in different environments? · Issue #5759 · symfony/symfony-docs · GitHub
[go: up one dir, main page]
Skip to content

Document how to use xdebug.file_link_format in different environments? #5759

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.

Sign up for GitHub

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

Jump to bottom
Closed
xabbuh opened this issue Oct 6, 2015 · 5 comments
Closed

Document how to use xdebug.file_link_format in different environments? #5759

xabbuh opened this issue Oct 6, 2015 · 5 comments
Labels
Waiting feedback

Comments

@xabbuh
Copy link
Member
xabbuh commented Oct 6, 2015

In symfony/symfony#14340 it was requested to be able to use the xdebug.file_link_format with a virtual machine. Is that something that we consider as a valuable contribution to the documentation (for example, explaining how to configure this value depending on your development environment)?
@xabbuh xabbuh changed the title Document how to use xdebug.file_link_format in different environments Document how to use xdebug.file_link_format in different environments? Oct 6, 2015
@BenjaminPaap
Copy link
Contributor

Personally I would not expect this in a symfony documentation. My first location would be the vendor of my IDE. The time I noticed that configuration option I searched the internet on how to set up my IDE to get this thing working (I failed 😄). And as mentioned in the comments of symfony/symfony#14340 this should be more a case for IDE vendors.

@dupuchba
Copy link

@xabbuh I think it's a good idea but I would see it in a "Tips" section

@javiereguiluz
Copy link
Member

In my opinion we shouldn't document this in the current Symfony documentation. If we implement a new strategy for the Symfony Docs regarding the virtual machines and we start adding articles related to them, then I'd change my opinion.

@nicolas-grekas
Copy link
Member

See #19807 for a Symfony-inside solution that is coming to 3.2

@javiereguiluz
Copy link
Member

Closing it as fixed by symfony/symfony#19807 and #6944.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Waiting feedback
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@javiereguiluz @nicolas-grekas @BenjaminPaap @dupuchba @xabbuh
0