John Blackbourn
John Blackbourn
I think I'd seen that previously but had forgotten about it. Let's close this then.
https://github.com/cftp/WP-Extension-Check
Sorry I haven't had any time to look into this further or reproduce on a different site. I'll try to find some time soon.
Neither myself nor a colleague can reproduce this now. Sorry I can't provide any useful info, I know how annoying that is. Here's some possible avenues if you do want...
This is most likely caused by Gravity Forms, which aggressively dequeues other JS and CSS assets on its admin screens because it thinks it's special. https://github.com/johnbillion/query-monitor/issues/325
I don't think I'm going to have time for this actually. Like I said, Cavalcade will work out of the box with this change but the addition of support for...
If I had to guess I'd say it's something that most people developing a custom block would find useful, but that's only a guess.
Correct but as far as I know (although I don't follow them closely) neither PSR-5 nor PSR-19 propose such a syntax. What alternatives are there?
The WordPress open source project uses an adjusted version of the hash syntax for its array-type parameters: ```php @param array $foo { @type string $bar This is a string @type...
Psalm and PHPStan have both adopted the short inline syntax: ``` @param callable(Type1, OptionalType2=, SpreadType3...):ReturnType $foo Bar ``` Frustratingly, this doesn't allow for descriptive information about the parameters passed to...