Allow usage of stdclass instead of object where it makes sense

This has now been implemented in Coder in ✨ stdclass is auto-corrected to object but it should not be Fixed .

Raising priority to major as now the documented coding standards are not in sync with Coder.

Next step: define the wording and necessary changes to coding standards documentation pages in the issue summary.

use the coding standard template

The next step here is to complete the proposed resolution section.

So yeah, we'd need to update this: https://www.drupal.org/docs/develop/standards/php/api-documentation-and-... →

To deal with this:

object (NOT "stdClass")

Adding link to current text and the current text.

Anyone know what 'stdClass' was excluded?

A bit more accurate title

I think I would rather disallow type-hinting with \stdClass at all to resolve this, then it not being allowed in the PhpDoc would not be a problem. Type-hinting on \stdClass seems like bad practice to me and it should be discouraged if it isn’t yet in our standards.

Anyone know what 'stdClass' was excluded?

Seems like this was written in a time when Drupal mostly used anonymous objects and we just wanted to document those as object in the PhpDoc, not as \stdClass. Actual type hints were not allowed in PHP at that time, so the question of a discrepancy between PhpDoc and in-code type hint never arose.
And we probably couldn’t think of a good reason to actually require a \stdClass object instead of any object with the required (public) properties – same as I do now.