Skip to content

Instantly share code, notes, and snippets.

View jrfnl's full-sized avatar
🐘
Herding 🐘

Juliette jrfnl

🐘
Herding 🐘
View GitHub Profile
@jrfnl
jrfnl / 20241006-phpcs-phpcompat-rfc-getdeclaredenums-ooexists.txt
Last active October 6, 2024 07:14
RFC GetDeclaredEnums: usage of combinations of *_exists() functions
FILE: antecedent\patchwork--2.2.0\src\Utils.php
------------------------------------------------------------------------------------------------------------------------------------------------------
FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
------------------------------------------------------------------------------------------------------------------------------------------------------
LINE 156: WARNING Detected use of combination of class_exists(), trait_exists() within same function body
(PHPCompatibility.RFC.OOExists.class-traitexistsInSameFunctionFound)
------------------------------------------------------------------------------------------------------------------------------------------------------
154: }
155:
>> 156: function classOrTraitExists($classOrTrait, $shouldAutoload = true)
@jrfnl
jrfnl / 20241006-phpcs-phpcompat-rfc-getdeclaredenums-getdeclared.txt
Created October 6, 2024 06:33
RFC GetDeclaredEnums: usage of get_declared_*() functions
FILE: algolia\scout-extended--v3.1.0\src\Helpers\SearchableFinder.php
----------------------------------------------------------------------------------------------------------------------
FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
----------------------------------------------------------------------------------------------------------------------
LINE 104: WARNING Detected use of get_declared_classes() (PHPCompatibility.RFC.GetDeclared.get_declared_classesFound)
----------------------------------------------------------------------------------------------------------------------
102: }
103:
>> 104: $this->declaredClasses = get_declared_classes();
105: }
@jrfnl
jrfnl / 20210917-notes-on-input-validation.md
Created September 17, 2021 18:11
Notes on input validation for WP Core

What is input validation ?

Checking for a variable/ array index:

  • Does it exist ?
  • Is it of the right type ?
  • Is the value usable for our purposes ?

Problem definition:

  • Lack of input validation throughout most of Core.
  • ... which is especially problematic in the context of filter hooks / callbacks.
@jrfnl
jrfnl / phpunit.bat
Created August 13, 2021 14:23
PHPUnit PHP/PHPUnit switching script example
@echo off
::
:: PHP ??? have Xdebug + Blackfire.
:: PHP 7.4.14 has Xdebug with coverage
:: PHP 7.4.15 has Xdebug with develop + trace
::
:set PHPBIN=C:\wamp\bin\phpcli_x86\php5.2.17\php.exe
:set PHPBIN=C:\wamp\bin\phpcli_x86\php5.3.29\php.exe
:set PHPBIN=C:\wamp\bin\phpcli_x86\php5.4.45\php.exe
:set PHPBIN=C:\wamp\bin\php\php5.5.38\php.exe
@jrfnl
jrfnl / reservednames.txt
Last active May 5, 2022 10:19
Reserved names used as parameter names in WordPress - Trac ticket: #55650 https://core.trac.wordpress.org/ticket/55650 - Last updated: 2022-05-05
Command used: `phpcs -ps . --sniffs=Universal.NamingConventions.NoReservedKeywordParameterNames --report=full,summary,source --extensions=php` (will not work by default)
FILE: src\wp-admin\includes\template.php
----------------------------------------------------------------------------------------------------
FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
----------------------------------------------------------------------------------------------------
907 | WARNING | It is recommended not to use reserved keywords as function parameter names. Found:
| | $parent
| | (Universal.NamingConventions.NoReservedKeywordParameterNames.parentFound)
----------------------------------------------------------------------------------------------------
@jrfnl
jrfnl / phpcs3.5-dev-upgrade-guide.md
Last active May 24, 2019 00:59
Draft: Upgrade guide to PHP_CodeSniffer 3.5.0 for sniff developers

Upgrade guide to PHP_CodeSniffer 3.5.0 for sniff developers

PHP_CodeSniffer 3.5.0 contains a lot of changes under the hood. For the most part these are non-breaking.

If you maintain an external standard, you have three options:

  • Maintain compatibility with older PHP_CodeSniffer versions [1]. In that case, there is probably nothing you need to do. Just make sure you check the BC-breaks section below just in case. All the "old" utility methods and properties will still work. They will however be removed in PHPCS 4.0.
  • Maintain compatibility with older PHP_CodeSniffer versions [2].
@jrfnl
jrfnl / phpcs3.5-changelog.txt
Last active March 23, 2019 22:48
Draft: PHP_CodeSniffer 3.5.0 changelog
- Squiz.Formatting.OperatorBracket.SpacingAfterMinus has been renamed to Squiz.Formatting.OperatorBracket.SpacingAfterSign
-- If you are referencing the old error code in a ruleset XML file, please use the new code instead
-- If you wish to maintain backwards compatibility, you can provide rules for both the old and new codes
- `Conditions::getCondition()` accepts both a single token type or an array of token types for the `$type` parameter, which has been renamed to `$types` to convey this. The parameter is also now optional.
Additionally, the new version of the method has an optional boolean `$reverse` parameter which allows to indicate whether to get the _first_ condition of a certain type or the _last_.
- `ObjectDeclarations::getClassProperties()` now has improved handling of class declaration code interlaced with comments and/or annotations
- `ObjectDeclarations::findExtendedClassName() and `ObjectDeclarations::findExtendedInterfaceNames()` will now return the class/interface names witho
@jrfnl
jrfnl / phpcs4-removals.md
Last active March 23, 2019 15:19
Draft: PHPCS 4.0 remove deprecated methods and properties

The following methods and properties have been deprecated in PHPCS 3.5.0 and should be removed in PHPCS 4.0.0:

Methods:

  • PHP_CodeSniffer\Files\File::hasCondition()
  • PHP_CodeSniffer\Files\File::getCondition()
  • PHP_CodeSniffer\Files\File::getClassProperties()
  • PHP_CodeSniffer\Files\File::findExtendedClassName()
  • PHP_CodeSniffer\Files\File::findImplementedInterfaceNames()
  • PHP_CodeSniffer\Files\File::getMethodParameters()
@jrfnl
jrfnl / 2018-WCEU-code-samples.php
Last active June 14, 2018 09:31
201805 WCEU Code samples
<?php
/*
* Example of translators comment for a text string with a single placeholder.
*/
/* translators: %s: the version number of a WordPress release. */
esc_html_e( 'Wordpress %s is awesome!' );
/*
@jrfnl
jrfnl / 20180611-phpcs-run-src-only-i18n-NOT-translatorscomments.txt
Created June 14, 2018 06:38
201806 WCEU list of other I18n issues for review
FILE: src\wp-admin\credits.php
--------------------------------------------------------------------------------------------------------------
FOUND 3 ERRORS AND 3 WARNINGS AFFECTING 3 LINES
--------------------------------------------------------------------------------------------------------------
68 | WARNING | Use of the "translate()" function is reserved for low-level API usage.
| | (WordPress.WP.I18n.LowLevelTranslationFunction)
68 | ERROR | The $text arg must be a single string literal, not "$group_data['name']".
| | (WordPress.WP.I18n.NonSingularStringLiteralText)
70 | WARNING | Use of the "translate()" function is reserved for low-level API usage.
| | (WordPress.WP.I18n.LowLevelTranslationFunction)