[experimental] Profile methods of view class #18
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 experimental and unfinished code, which adds profiling of all methods of view class. The PR contains commits from #17, but I can also rebase them out. This functionality is much simpler than the whole changelog - only the last commit.
I wanted to know more about my views timing, so I also runtimes of the view functions:

It is not perfect yet - for example the view has to be executed twice in order to patch the class correctly. I am not sure how to solve this, but I also didn't give it much time yet.
Also it probably doesn't work for function base views, but I don't think it would be such problem to fix it.
I know, that this might be out of scope of this DJDT panel, but I would also don't want copy the code out of this package, because most of the code is shared. I also didn't find other DJDT panel with this functionality - the profiling panels I found were hard to set-up and did produce very complicated and unclear output.
So what do you think? Should this be made into this panel (which would then be
view-profiler
rather thantemplate-profiler
)?