- Status changed to Needs work
over 1 year ago 2:59pm 29 March 2023 - 🇺🇸United States smustgrave
#102 appears to be missing a number of changes from #97 can it be documented why?
Also the interdiff is the same size of the patch?
- 🇳🇿New Zealand quietone
Thanks for the interest in this work. However, as pointed out in several comments the work here is to address comments #92, #93, #94. And #93 suggests that we don't implement this sniff at all!
I am changing the status to active so emphasize that the work here is to resolve #92, #93, #94. Also, updating credit per How is credit granted for Drupal core issues → .
- Status changed to Active
over 1 year ago 11:52pm 29 March 2023 - 🇷🇺Russia zniki.ru
I checked #94 and I totally agree that we need to update code sniff rule Drupal.Commenting.InlineComment.SpacingAfter to work with examples provided in #79.
Do we have issue for that?Do I understand it right, before we have agreement or code sniff rule will be update, no further patches should be attached to this issue?
- Status changed to Postponed
about 1 year ago 6:43am 17 November 2023 - 🇳🇿New Zealand quietone
@zniki.ru, thanks for the interest in coding standard issues! For some background, there is a Coding Standards project → where the community discusses changes to the Drupal Coding standards. Changes agreed to there usually require a change to the Coder project to implement a new sniff or create a new one. Once, that is done, then we have issues it the core queue to implement the change. There is also the #coding_standards channel in Drupal Slack where coding standards are also discussed.
There is an issue in the Coding Standards project discussing changing this standard, #2464123: Remove the requirement that no blank line follow an inline comment → . That issue is being worked on so maybe we should postpone this on that issue. I do want to avoid double work. I am adding that as a relating issue and postponing this on that issue.