Open rebeccahum opened 3 years ago
VIPCS could benefit from having a custom IniSet sniff...similar to https://github.com/WordPress/WordPress-Coding-Standards/blob/41f5a9c66ff814863bc479fb52fd6cd1abc87e28/WordPress/Sniffs/PHP/IniSetSniff.php#L55-L65, but we want to be able to customize the whitelist property for the below values:
WP already manages sessions but we have some clients that want to control PHP sessions via custom code.
ini_set('session.cookie_httponly', true); ini_set('session.cookie_secure', true); ini_set('session.use_only_cookies', true);
https://github.com/WordPress/WordPress-Coding-Standards/issues/1993
As the WPCS property which controls the "allow list" is protected, I think we can simply extend the WPCS sniff and add those extra ini settings to the property from the sniff constructor.
protected
Describe the solution you'd like
VIPCS could benefit from having a custom IniSet sniff...similar to https://github.com/WordPress/WordPress-Coding-Standards/blob/41f5a9c66ff814863bc479fb52fd6cd1abc87e28/WordPress/Sniffs/PHP/IniSetSniff.php#L55-L65, but we want to be able to customize the whitelist property for the below values:
WP already manages sessions but we have some clients that want to control PHP sessions via custom code.
What code should not be reported as a violation?
Additional context
https://github.com/WordPress/WordPress-Coding-Standards/issues/1993