expression-language | Provides an engine that can compile and evaluate expressions

That composer.json file is a bit of a mess. Some Symfony packages on 5.3, some even on 5.1, and many on 6.

Also you are controlling Symfony versioning from extra.symfony.require, and at the same time from the discrete version constraints. You include some packages that no longer exist on 6.0 (symfony/security-guard), and are missing some that should be installed on a 6.0 version.

It's simply not on an installable state.

I've managed to make it installable changing it like this:

Unfortunately doing this reliably (as you've noted) is not really ideal using only Expression Language.

The most reliable method to do this would be:

• UpdateAttribute to set a new attribute with ${now()}
• ExecuteGroovyScript with a simple piece of Groovy to
  • Get the attribute
  • Use Groovy date/time functions to safely add to the date
  • Set the attribute value

Cookbook Part 1 covers how to work with FF Attributes.

E.g.

As in my comment, columns are defined by the objects properties when using Export-Csv or Export-Excel. If you were to replace the leading spaces, slashes, pipes, etc with tabulations the end result after exporting to CSV or Excel would not look like the spreadsheet you've added to your question, the export would be a one column file and each cell would have a different padding (depending on the nesting of the files).

In my opinion, even though more code is required, is to use recursion instead of regex replace for this. I'll use my /etc/ folder for this example.

• So, step by step, define a Recursive function to scan the directories first:

Try changing composer.json

From:

The solution is to execute:

You have conflicting requirements.

On extra.symfony.require you say you want 5.3.*.

But on your individual Symfony requirements you are specifying either ^5.2 or 5.2.* (and in some cases ^5.3 as well).

When a project uses Symfony Flex (as is your case), the presence of extra.symfony.require will be used to restrict what package versions to install for many/most Symfony packages. But only if you do not declare a specific version on your require section.

In this case, you are already specifying a version on the 5.* range on extra.symfony.require. Leave that one like that, and just use * as a version constraint for all the other Symfony Packages in the require section.

(Note that's it's not really all, since some packages are not managed by Flex, just update the ones that have versions declares in the 5.* range)

You can split the content to several lines then use fragment.index to prepent the counter to the lines. After that you can merge them again.

The Flow:

GenerateFlowFile:

SplitText:

ReplaceText:

MergeContent: Don't forget to add a new line (Shift+Enter) to Demarcator attribute.

Result:

You can use ${Fragment.index:minus(1)} if you want to count from zero.

As you can read in an issue posted in the issue tracker of doctrine/cache, that class has been deprecated in v1 of that package, and removed in v2.

If you still want to use that class, run composer require doctrine/cache "^1.12" to install a version of that package from the v1 branch.

On the long run, you should check where your application requires that class and search for alternatives. If you need help with that, please share more details.

You have two problems:

• You have Symfony '5.3' installed, which was released just one day ago.
• You are using PHP 8, which is not supported by Sylius. By using PHP 8, you end up installing versions of dependencies that are not compatible with Sylius.

Since the current version of Sylius supports up to 5.2, and PHP ^7.3, you'll have to either downgrade to Sf 5.2 and PHP >= 7.3 && PHP < 8, or wait a some time so support for Sf 5.3 and PHP >= 8 is baked in.

I would recommend using the standard Sylius installation, but trying to install Sylius with the recommended docs way (composer create-project sylius/sylius-standard acme) when using PHP 8 also fails. But downgrading to PHP 7.4 and running the create-project command does work.

The project seems to have entered the dependency hell stage of development.