I'm mixed on this one. This will create more changes than required when syncing recipes, increasing the burden of the task.
You can achieve the same by first removing symfony.lock, then running with --force.

Sorry I closed by mistake.

You can achieve the same by first removing symfony.lock, then running with --force.

You're right in the end the results are the same but i think this is only a workaround.

For example in the help message of the --force option it says Ignore the "symfony.lock" file and overwrite existing files.

I'm mixed on this one. This will create more changes than required when syncing recipes, increasing the burden of the task.

Do you mean with it will create more changes than required in the project source code or in the source code of flex?

Today i checked the recipes of a project and there was a update for the symfony/framework-bundle available.

If you're running composer recipes:install symfony/framework-bundle you get the message:

Recipe(s) already installed for: symfony/framework-bundle
Re-run the command with --force to re-install the recipes.

No recipes to install.

Then i run the command again with the option --force and it does exactly what I'm expecting after I read the help/info message. It re-installs the complete recipe and overrides all files or add missing ones. But that is easy to solve if you're using i.e. Git :D :)

Did #756 solve this?