@fastslack Is this even supposed to work? Joomla is distributed with the package versions that it supports, wouldn't composer get newer versions that are untested?

I guess this would be a real issue if we decide to ship a newer version of phputf8 with Joomla.

Just my 2 cents :)

@roland-d I used the default composer.json that come in Joomla! CMS distribution. I supposed that should be compatible but really i'm not sure about this.

@fastslack this is because the phpuft8 is shipped with the string package and the core itself. I'm not sure if we can simple remove the version shipped with the CMS. Maybe @mbabker can have a look here?

The phputf8 library located at libraries/phputf8 was left in place when the Composer integration was set up so as to not break extensions including files from that location. It should be considered deprecated, the version at libraries/vendor/joomla/string/src/phputf8 should be used going forward.

FWIW there are some functions in the phputf8 library that are not made available through the StringHelper class so you'd need to manually load the correct files. But those are honestly more of an exception than a rule.

Also to add, phputf8 has been treated differently than other libraries because other library code is included in other ways (either direct includes or autoloader rules). As a massive collection of functions, these files aren't autoloadable in the same sense that classes are. The latest tag of the Framework's String package does tell Composer to auto include all the files the StringHelper class is dependent on which allowed removing a lot of include checks from the class, but again this doesn't cover the entire library.

Is there anything to do here or is it to be closed @mbabker

Closed at this time