Checks for INTL_IDNA_VARIANT_UTS46 #1440
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #1439
Since ICU, which provides the
INTL_IDNA_VARIANT_UTS46
may not be kept up to date the same as PHP, a separate check here will prevent the undeclared constant warning.The downside is
idn_to_utf8
function defaults to usingINTL_IDNA_VARIANT_2003
which would then throw a deprecated warning in PHP 7.2+. If PHP 7.4, it is planned that the default will beINTL_IDNA_VARIANT_UTS46
which would likely return the original issue.@westonruter What would you prefer? Checking for UTS46 and taking the deprecated in PHP 7.2 for sites running ancient ICU or check for the UTS46 variant along with the
idn_to_utf8
exists check? Or a third option?