Invalid PHPDoc blocks about gravity-forms-stubs HOT 7 CLOSED

Is it a good ide to replace @param $entry 👉🏻 @param mixed $entry??

afaik an $entry is always either an array or some falsy (null | false | '' ), depending on the particular method. No need to go full mixed.

from gravity-forms-stubs.

Fixing 369 invalid @param tags require several days of work from GF authors.

from gravity-forms-stubs.

Is it a good ide to replace
@param $entry 👉🏻 @param mixed $entry??

from gravity-forms-stubs.

But this is an automatic repo. No one will fix it manually for every release :(

Is mixed better than an invalid docblock? (theoretic question)
I am not planning to spend time on this repo.

from gravity-forms-stubs.

Sorry I wasn't clear. I think mixed is better than an invalid docblock, but specifically for $entry, you should be able to string-replace to @param array|string|false|null $entry.

from gravity-forms-stubs.

GF's code quality is abysmally low. It has no API to serve older releases.
This is money making and targeting non-experts only.
So I am out.

from gravity-forms-stubs.

Please see https://community.gravityforms.com/t/new-package-gravity-forms-stubs-for-ide-autocompletion-and-static-analysis/15577

from gravity-forms-stubs.