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
The composer create-project command uses apostrophes ' as delimiters by default. In my case, I've added escaped apostrophes in the description during the setup process.
The setup/build task transforms the delimiters into double quotation marks " but leaves the string unchanged. The string is now malformed JSON and can no longer be processed. This leads to an error in vendor/yootheme/starter-utils/src/StringHelper.php:71 when json_decode is called.
Using double quotes would fix the issue in this case, but might lead to similar issues.
The .env-file gets read using parse_ini_file(), which is not really designed to be used with .env-files. Switching to a purpose-built parser might be better.
The text was updated successfully, but these errors were encountered:
The Task runner reads the .env file and passes the variables as json to the placeholder function.
Unfortunately we can't influence the json here and you need to manually change the quotes for the "description" in the .env file when a single quote is needed.
Like you write changing the quotes to double quotes in general would lead to the same issue.
The parse_ini_file function is only used when the Joomla update.xml file is created, it's not involved here.
The
composer create-project
command uses apostrophes'
as delimiters by default. In my case, I've added escaped apostrophes in the description during the setup process.The setup/build task transforms the delimiters into double quotation marks
"
but leaves the string unchanged. The string is now malformed JSON and can no longer be processed. This leads to an error invendor/yootheme/starter-utils/src/StringHelper.php:71
whenjson_decode
is called.Using double quotes would fix the issue in this case, but might lead to similar issues.
The
.env
-file gets read usingparse_ini_file()
, which is not really designed to be used with.env
-files. Switching to a purpose-built parser might be better.The text was updated successfully, but these errors were encountered: