-
More docblocks are needed for the top layer APIs that are used the most. At the very least simple `param` and `return` tags for code completion in IDEs.
-
There have been conversations going on regarding docblocks and usage within projects at Liftopia. The place to have those conversations is here. We have a style guide adopted by the team which does ap…
-
There's some inconsistencies and things like missing periods/punctuation. We should fix that according to https://docs.backdropcms.org/doc-standards#general
Specifically these rules:
> - All summa…
-
Hello,
I know you dislike that, but it would be very useful for many people. I can handle it but I want you to tell me what you think about before doing anything.
Proposal:
- No docblock for in…
-
### Summary
Some of the classes / models do not contain type declarations.
Specifically model scopes and relationships are currently lacking argument and return types.
IMHO adding them would help…
-
Fantastic! Another small detail - documentation block after members show `/
-
It would be nice if the optimize-use and fix-classnames refactoring would also take care of DocBlocks and the types/classnames in it.
Particularly types for the `@returns` and `@param`-tags are very …
-
**API Platform version(s) affected**: 4.0.9
**Description**
**How to reproduce**
```php
#[ApiResource]
class Test {
/** @var array */
public array $foos;
}
class Foo {
…
-
Initial PR for this issue: https://github.com/backdrop/backdrop/pull/3113
The documentation we use for preprocess functions is inconsistent all over core. [Drupal 8 adopted a new standard](https:/…
-
Seriously, am I the only one who finds this completely strange? I thought good documentation was all about multiline blocks like
```
/**
* Description
* @param [someOption] {boolean} description]
…