Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Moshe,
despite the fact the D6 v1.18 release is saying it fixed all coder module warnings, i just tested it today and a huge list is presented. I used "minor" and "D5 -> D6" options.
regards,
massa
Comment | File | Size | Author |
---|---|---|---|
#15 | devel-coder-269984-15.patch | 60.68 KB | jacob.embree |
|
Comments
Comment #1
brmassa CreditAttribution: brmassa commented21 weeks later and no answer... closing the issue
Comment #2
moshe weitzman CreditAttribution: moshe weitzman commentedWhat's to anwser? You reported an issue. Noone has worked on it.
Comment #3
brmassa CreditAttribution: brmassa commentedMoshe,
sorry. Since no one replied, i thought it was: 1* already fixed or 2* no interest on such level of "problems". Good to hear someone is aware of it.
regards,
massa
Comment #4
mgiffordIt's still an issue in the latest code too. This should be fixed at least when the code is being reviewed for D7 migration, then backported to D6.
Comment #5
kenorb CreditAttribution: kenorb commentedComment #6
kenorb CreditAttribution: kenorb commentedComment #7
salvis7.x-1.3 is of no interest here. If anyone is going to do anything then it'll be against 7.x-1.x-dev.
Coder (and PHP) evolve, too, and it's normal that new warnings and notices pop up over time.
Comment #8
jacob.embree CreditAttribution: jacob.embree at St. Louis Integration commentedCoding standards fixes are kind of fun. If you're willing to take them then I'll do more. If you prefer I start with Drupal 8 I'll do that too.
This patch contains mostly documentation improvements and does not include
devel_generate
.Comment #9
jvogt CreditAttribution: jvogt as a volunteer commentedHey jacob.embree,
Your patch (#8) applied cleanly for me, but I'm still getting a lot of warnings from phpcs. I'm super new to Coder and phpcs, so forgive me if I'm all wrong about this. It looks like we're sniffing the code in different ways, so that may have something to do with it. I ran the following per these instructions:
phpcs --standard=Drupal --extensions='php,module,inc,install,test,profile,theme,css,info,txt,md' devel
Attached are two files with phpcs output. cr-output.devel.txt are the results without the patch and the other is after the patch was applied. devel_generate excluded.
Comment #10
jacob.embree CreditAttribution: jacob.embree at St. Louis Integration commentedzorya,
I don't know how the maintainers want to do it, so I figured on doing large chunks at time rather trying to fix every coder issue in one patch since there are so many. My patch has just documentation fixes. I'll probably keep plugging away at it, and if I ever manage to fix everything then I'll upload that patch.
Comment #11
jvogt CreditAttribution: jvogt as a volunteer commentedAh, gotcha. It's quite the hefty task. Makes sense to wait and see what the maintainers want.
Comment #12
salvisI'm a bit on the fence here...
Generally, we want to spend most of the effort on the current version (read: D8).
We would like Devel to be a model of good code, but OTOH, sweeping changes mess up the version history. Sometimes we need to dig into the praise/blame history to understand why something is as it is, or even to just find the issue that produced a given line of code, and big time changes make this more difficult.
I've had a brief look at your #8 and, as you say, it's mostly documentation fixes, which is less of a problem for the version history. I lean towards committing #8 after taking a closer look, but I'd like to get Moshe's view, especially before you turn to work on the code.
Since you've written so many docblocks, you must know Devel better than we do by now. :-) As with any piece of software, I'm sure there are still bugs here and there--please don't hesitate to open issues if you find something that isn't right. Also, many of the rules are designed to avoid coding mistakes, and massaging the code to comply with the rules may definitely turn up hidden bugs.
Moshe?
Comment #13
moshe weitzman CreditAttribution: moshe weitzman at Commonwealth of Massachusetts commentedI'm fine either way. Up to you, salvis. Thanks everyone.
Comment #14
salvisNeeds re-roll, then I'll commit it.
Comment #15
jacob.embree CreditAttribution: jacob.embree at St. Louis Integration commentedComment #17
salvisThanks, jacob.embree!
Nice catch with the missing return.
I put back the commented dpm() calls that you removed in DNA. There's a lot of value in them, and if I ever had to do any debugging on that code again, I would need to waste time to re-develop them. I know that the Coding Standard says otherwise, but in this case I refuse to comply.