Closed stefantalen closed 7 months ago
Thanks for the PR 😍
Define the SYMFONY_ENDPOINT
environment variable:
# On Unix-like (BSD, Linux and macOS)
export SYMFONY_ENDPOINT=https://raw.githubusercontent.com/symfony/recipes/flex/pull-1272/index.json
# On Windows
SET SYMFONY_ENDPOINT=https://raw.githubusercontent.com/symfony/recipes/flex/pull-1272/index.json
Install the package(s) related to this recipe:
composer req 'symfony/flex:^1.16'
composer req 'symfony/framework-bundle:^7.0'
Don't forget to unset the SYMFONY_ENDPOINT
environment variable when done:
# On Unix-like (BSD, Linux and macOS)
unset SYMFONY_ENDPOINT
# On Windows
SET SYMFONY_ENDPOINT=
In order to help with the review stage, I'm in charge of computing the diff between the various versions of patched recipes. I'm going keep this comment up to date with any updates of the attached patch.
Actually the option has been backported to 3.4 some time after it was introduced (see https://github.com/symfony/recipes/pull/738 & https://github.com/symfony/symfony/pull/35605). Given the situation into which the mentioned error can happen are edge cases (unmaintained versions that new projects should not rely on), I think there is nothing we should do here hence I'm going to close. Thanks for your understanding
@chalasr Thanks for the extra info! I agree with your statement that new projects should not rely on unmaintained versions.
However, in our situation we are in the process of upgrading a Symfony 3.4 project to 6.x with intermediate steps at
Having configuration issues because of recipes, adds some noice to the process.
Because this option has been backported, the least we could do (for DX) is add the configuration option in comments for 4.0 or add a comment to the addition in 3.4 stating it was backported and doesn't work when upgrading 3.4 to 4.0.
The
cookie_samesite
option is not available before Symfony 4.2, having this in the recipe results in an error: