- 🇳🇿New Zealand quietone
I worked on the core issue 📌 Fix 'Drupal.Commenting.VariableComment.VarOrder' coding standard Postponed today and reporting back here.
The Drupal coding standards page api-documentation-and-comment-standards#order does not mention @code in the order of sections. Should it be considered a section?
Can make an in issue in the Coding Standards project so that can be discussed.
Core does not have any '@copyright' or '@license' in doc blocks. So, that point seems to be outdated.
And '@link .. @endlink' is reported as an error. But I think this is correct for the Variable comment block where the explanation is after @var.
Also, there were no instances in Drupal core where an '@link .. @endlink' was moved as a result of enabling the sniff.
So, for me I would go with won't fix on this.
- Status changed to Closed: won't fix
4 months ago 9:29am 3 August 2024 - 🇦🇹Austria klausi 🇦🇹 Vienna
I agree - and I don't think we will need @var comments in the future as now you must always specify the type of your class property as type hint (at least for new code). Eventually we can remove the @var coding standard and enforce property type hints with a sniff from Slevomat.