write the inspect variables guide page - #16
Merged
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
Sign up for free
to 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.
Replaces the inspect variables placeholder with the full guide page, IDE-agnostic throughout.
Covers stack levels and selecting an outer frame, what the variables panel shows and why arrays and objects arrive collapsed, and the three variable groups.
Verified against
handler_dbgp.c:PHP_USER_CONSTANT, so PHP's own constants and those from extensions never appear — which is part of why the group is so often emptymax_children,max_dataandmax_depthare negotiated per session viafeature_set, so the editor's values override the ini defaults. The page sends people to their editor's settings rather than tophp.ini.