That's an issue, indeed. I've already thought about it and the only solution I can think of is to mark types explicitly (see jsdoc: `{int}`). This would also allow renderers and IDEs to link types even if they are part of the description. But this is another topic.
Am 05.10.2019 07:30 schrieb Ben Mewburn <b...@mewburn.id.au>:
I see the reasoning but how is a phpdoc parser going to handle--/** @return ImNotATypeImADescription make sure you parse me correctly */function func(): int {}
On Wednesday, October 2, 2019 at 6:40:06 PM UTC+10, Nils Rückmann wrote:The type declaration in DocBlocks dates back to a time when type-hinting was not part of the language.IMO there is no reason to keep the type as mandatory part of tags like @param.We should be be allowed to omit the type part if it does not add any new information.Affected tags:@param@returnAny thoughts about this? Could not find an ongoing (or ended) discussion about this, if i missed it, please point me to it.Regards,
Nils
You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/faa42671-f37e-46e0-a1a0-4eda2f764502%40googlegroups.com.
You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/a69fe1d6-5a89-4cdb-b0fe-6fc20a0fcb84%40email.android.com.
