You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the Unicode data generators (under tools/) and Unicode addons, rename isBmpLast as the more descriptive hasOrphanHighSurrogatesAndAstral. It's only used for category C and property Any, so the long name doesn't matter.
Or just hasOrphanHighSurrogates and let Unicode Base know to also check whether there is astral data before flipping the order of bmp and astral data.
Or just hasOrphanSurrogates and let Unicode Base know to also check whether there is astral data before flipping the order. This would mean attaching this prop in more cases where it isn’t currently useful (either because there’s no astral data or there are only low surrogates), but that’s probably not so bad.
The text was updated successfully, but these errors were encountered:
I don't think this should be treated as a breaking change, since isBmpLast is unlikely to be used by any existing addons outside of the official XRegExp Unicode addons (which themselves barely use it).
In the Unicode data generators (under
tools/
) and Unicode addons, renameisBmpLast
as the more descriptivehasOrphanHighSurrogatesAndAstral
. It's only used for categoryC
and propertyAny
, so the long name doesn't matter.hasOrphanHighSurrogates
and let Unicode Base know to also check whether there is astral data before flipping the order ofbmp
andastral
data.hasOrphanSurrogates
and let Unicode Base know to also check whether there is astral data before flipping the order. This would mean attaching this prop in more cases where it isn’t currently useful (either because there’s no astral data or there are only low surrogates), but that’s probably not so bad.The text was updated successfully, but these errors were encountered: