Export the names of the functions used in each element #85
Conversation
This file contains 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
| @@ -58,7 +61,9 @@ class File_Reflector extends FileReflector { | |||
| * We also check function calls to see if there are any actions or hooks. If | |||
| * there are, they are added to the file's hooks if in the global scope, or if | |||
| * we are in a function/method, they are added to the queue. They will be | |||
| * assinged to the function by leaveNode(). | |||
| * assinged to the function by leaveNode(). We also check for any other function | |||
There was a problem hiding this comment.
Existing typo here - assigned
Rarst
added a commit
that referenced
this pull request
Apr 8, 2014
Export the names of the functions used in each element
Merged
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.
See #79
This is a proof of concept for exporting the functions used by each element. I've made no attempt to import this data here, because we haven't decided the best way of doing that yet. The idea is to maybe go ahead and get this committed so folks can hack away on the importing/display part.
Notes:
do_actionandapply_filtercalls, even though they are already being exported as hooks. My thinking here is that they will be weeded out on import or display as needed.