Directory sizes

88  orders
92  system-status
96  legacy
96  query
108 locking
128 phpqrcode
320 settings
444 webapi
632 addon
672 splash-page
760 fields

Maybe distribute fields in a separate stubs file??

Hello @SebKay! 👋🏻

Would you contact GF developers to get a license for these stubs?
https://www.gravityforms.com/open-support-ticket/account/

https://github.com/php-stubs/wordpress-stubs/blob/master/finder.php

@SebKay I think GF is a huge mess even compared to other products in the WordPress ecosystem.
In php-stubs org I follow a rule that deprecated and compatibility parts should be excluded from stubs.
There are class files with side-effects 🤯 new GFFormLocking(); ... and multiple classes in 1 file.
PHPStan on Level 0 says Found 131 errors

Could you look around in the GF plugin for included/excluded files/directories?

https://gravityapi.com/wp-content/plugins/gravitymanager/api.php?op=get_plugin&slug=gravityforms&key=$PLUGIN_GF_KEY

the response is a serialized PHP array

$i=unserialize(stream_get_contents(STDIN));
echo $i["download_url"];

Signed URL: https://s3.amazonaws.com/gravityforms/releases/gravityforms_2.6.7.zip?....

I figure you generate the stubs in this package by running the PHP Stubs Generator on the latest GF code.

This is a difficult one. GF defines this function to only have 2 args ($filter and $value), which is reflected in the stub.

However, the function calls func_get_args() to get additional arguments (up to 9 of them). GF should change the function definition (and it's DocBlock) to use the variadic ... token. I don't know why they haven't done so.

For the time being, I have modified the stubs installed for one my GF addon plugins that calls gf_apply_filters() as be follows:

    /**
     * Gravity Forms pre-processing for apply_filters
     *
     * Allows additional filters based on form and field ID to be defined easily.
     *
     * @since  Unknown
     * @access public
     *
     * @param string|array $filter The name of the filter.
     * @param mixed $value The value to filter.
     * @param mixed ...$additional_args Additional arguments.
     *
     * @return mixed The filtered value.
     */
    function gf_apply_filters($filter, $value, ...$additional_args)
    {
    }

I'm sure it would be too much trouble for you to manually modify the generated stubs that you generate every time a new version of GF is released. But I just wanted to open this issue to raise the possibility.

https://github.com/php-stubs/acf-pro-stubs/blob/7e44b653bd72e5eebf725f3af6b5afaae3039dcf/generate.sh#L30-L43

There are ~100 invalids only from this type-less param type.

grep -r '@param\s*\$' | wc -l

🤯

CR-s remain in PHPDoc blocks.

Hey @szepeviktor,

I was planning on attempting my own release of GF + extension stubs, but I'd much rather contribute to an existing /official project.
Is this repo something you're still working on (i see open issue, but no code), and if so how can I help?

@justlevine Please add a "thank you for the license" section to the top of README