Closed
Conversation
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the Core Committers: Use this line as a base for the props when committing in SVN: To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This is a follow-up to this topic in 2025
Now that we are using XDebug 3, the original patches were deprecated.
https://xdebug.org/docs/upgrade_guide
Now the issues that @pento was raising have been resolved since no
remote_enableis needed anymore and the integration, is mostly straight forward.I'm submitting a new patch to enable the setup of Xdebug by default without requiring people to touch this file that is not ignored by .git by default. But Xdebug is not enabled by default since both
LOCAL_PHP_XDEBUG=trueandLOCAL_PHP_XDEBUG_MODE=debugare required for Xdebug to work, so in this regard, the user is "safe" by deafult.But having to manually untrack the
tools/local-env/php-config.inifile (in a development build, which theoretically Xdebug should be an staple for all developers), doesn't make any sense to me.Pinging @desrosj as he introduced the latest changes in Xdebug
.env.variables@johnbillion and @whyisjake as they touch this report back in the day.
Maybe it never progressed because of the concerns that @pento raised that are not valid any more.
Trac ticket: https://core.trac.wordpress.org/ticket/49953
This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.