Change Details

The codesniffer sniff `FunctionCommentSniff` does emits warnings (`MissingDocumentationPublic`, `MissingDocumentationProtected`, `MissingDocumentationPrivate`) when a function has parameters or is a "getter". But what about a function without params that returns a value but is not named `get*`? Should this function does require documentation of the return value? If {T258925} get fixed a possible return type hint should not require documentation.

The codesniffer sniff `FunctionCommentSniff` emits warnings (`MissingDocumentationPublic`, `MissingDocumentationProtected`, `MissingDocumentationPrivate`) when a function has parameters or is a "getter". But what about a function without params that returns a value but is not named `get*`? Should this function require documentation of the return value? If {T258925} get fixed a possible return type hint should not require documentation.

The codesniffer sniff `FunctionCommentSniff` does emits warnings (`MissingDocumentationPublic`, `MissingDocumentationProtected`, `MissingDocumentationPrivate`) when a function has parameters or is a "getter". But what about a function without params that returns a value but is not named `get*`? Should this function does require documentation of the return value? If {T258925} get fixed a possible return type hint should not require documentation.