Skip to content

[Sync-En] ext/mbstring: clarify the ValueError conditions of mb_*code_numericentity - #1220

Open
lacatoire wants to merge 1 commit into
php:masterfrom
lacatoire:sync-en/1206-mbstring-numericentity
Open

[Sync-En] ext/mbstring: clarify the ValueError conditions of mb_*code_numericentity#1220
lacatoire wants to merge 1 commit into
php:masterfrom
lacatoire:sync-en/1206-mbstring-numericentity

Conversation

@lacatoire

@lacatoire lacatoire commented Sep 2, 2026

Copy link
Copy Markdown
Member

Translation of php/doc-en#4852 (commit 3505aae): the errors section and the 8.4.0 changelog entry of mb_decode_numericentity and mb_encode_numericentity now say that map may hold any value implicitly convertible to int, not only integers.

Both pages also pick up php/doc-en#4708 (commit 0bb8d1a), the code style pass on the examples: it is the later commit on these two files, so it is the hash EN-Revision has to declare.

Fixes: #1206

@lacatoire
lacatoire force-pushed the sync-en/1206-mbstring-numericentity branch from 124e063 to 0ec948b Compare September 3, 2026 11:41
@lacatoire lacatoire changed the title [Sync-En] ext/mbstring: mb_*code_numericentity Clarify the ValueError conditions (#4852) [Sync-En] ext/mbstring: clarify the ValueError conditions of mb_*code_numericentity Sep 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Sync EN] ext/mbstring: mb_*code_numericentity Clarify the ValueError conditions (#4852)

1 participant