Currently the functions provided by devel not allow to fully use the dumper system in procedural code; for example is not possible to select a specific plugin when you dump a variable. The idea is create some (prefixed) functions that allow to fully use the dumper system:
- devel_dump()
- devel_export()
- devel_message()
- devel_debug()
Note: the not replace the devel's existing functions
Once these functions are in we should make use of they in all the procedural code. The advantages of doing that are:
- fully use the dumper system from procedural code
- more intuitive names and better documentation
- prefixed functions == no more conflict with other modules or libraries
- the calls to devel.dumper
are not more scattered in all devel functions. If we want to make a change, we could touch only these functions
- we can remove ::dumpOrExport from DevelDumperManager/Interface
Comment | File | Size | Author |
---|---|---|---|
#2 | add_functions_that-2840373-2.patch | 2.74 KB | willzyx |
|
Comments
Comment #2
willzyx CreditAttribution: willzyx commentedComment #3
moshe weitzman CreditAttribution: moshe weitzman commentedWhen would we use these in our own code? These wrappers seem useful to devs doing debugging.
Comment #4
willzyx CreditAttribution: willzyx commentedwe can use it in all the devel debug functions (dpm() , kpr() etc)
for example this
can be converted to use the new function
the advantages of doing that are described in the IS :)
Comment #5
moshe weitzman CreditAttribution: moshe weitzman commentedStill needed? LGTM
Comment #7
willzyx CreditAttribution: willzyx commented