Juliette

> I wasn't thinking of the 8.5 moving target when I asked. Even 8.3 is still a moving target - NEWS still gets updates and once in a while includes...

Work in Progress branches which should help to address this when the time comes: * [WAIT-VIPCS4.0/feature/849-remove-deprecated-properties-methods](https://github.com/Automattic/VIP-Coding-Standards/tree/WAIT-VIPCS4.0/feature/849-remove-deprecated-properties-methods) * [WAIT-VIPCS4.0/feature/849-functions-dynamiccalls-remove-deprecated-sniff](https://github.com/Automattic/VIP-Coding-Standards/tree/WAIT-VIPCS4.0/feature/849-functions-dynamiccalls-remove-deprecated-sniff)

Wondering the same, but more than anything hoping that @rhysd is okay. Life happens and we don't know what's going on (and it's none of our business either), but that...

@kekmitkep Please include information about which sniff(s) this request is for. > There are also multiple other usescases where this could be an issue. Again, please include information about which...

@TimWolla Good point. Thanks for adding that comment. In that respect, just to satisfy my own curiousity, how does the `#[AllowDynamicProperties]` attribute work, as that **_does_** apply to child classes...

> > For native PHP attributes, this is likely to lead to a Fatal Error on the PHP versions which didn't allow for the "new" construct yet, so I believe...

WordPressCS is not yet compatible with PHPCS 4.0. The version constraints in the `composer.json` reflect that. Work is on the way in the background to change that, but please be...

@frederikkempe Thanks, but in this case, @rodrigoprimo is the one doing the bulk of the work 🦸🏻‍♂️

That's 100% the idea for the future, but not the highest priority at this moment. If and when this will happen, it will be a GH Pages based website using...

P.S.: if you want to volunteer to take on the sub-project of getting a first version of that website up and running, I'll happily take you up on it ;-)