-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[Form] Move symfony/intl to require-dev #29229
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I am not sure if we can possibly detect this case. We would need to determine whether |
maybe it can be added as a default dep in the FW recipe? So at least the user is able to control it and remove if necessary. |
Suddenly removing the dependency would break at runtime. Given form is the only component having |
understood we might take this legacy for granted, but i still think we should try making it a dev-dependency long-term and aim for smaller packages. basically im still thinking if we can detect where sf/intl comes from, perhaps based on the current autoloader 🤔 otherwise meh :( |
Let's close this because of the reasons given by Robin (and the concerns expressed by Christian). Thanks. |
This PR was submitted for the master branch but it was merged into the 4.3 branch instead (closes #133). Discussion ---------- enable symfony/intl See symfony/symfony#29229 does it make sense? Next we'd move symfony/intl from require to require-dev in symfony/form. Commits ------- 310cb83 enable symfony/intl
This PR was squashed before being merged into the 5.3-dev branch. Discussion ---------- [Form] Remove hard dependency on symfony/intl | Q | A | ------------- | --- | Branch? | 5.x (or 6.0) | Bug fix? | | New feature? | no | Deprecations? | yes | Tickets | Fix #39596 | License | MIT | Doc PR | symfony/symfony-docs#15026 This was voted down in 2018 (#29229) and will revert #29720 by @chalasr. I reopen it because the Form component is way less dependent on Intl component now. Im hesitant if we should do this in 5.x or 6.0. If a user don't have `symfony/intl` installed, they will get an error in runtime. That is something that speaks for doing it in 6.0. Could I get some opinions? ### TODO - [x] Update `UPGRADE-x.x.md` Commits ------- f90d3ec [Form] Remove hard dependency on symfony/intl
In #28610 we've added exceptions to give better error messages in case one uses a form type that relies on symfony/intl. The problem is this can never happen, as sf/intl is a hard requirement per composer.json
symfony/src/Symfony/Component/Form/composer.json
Lines 18 to 21 in dbf053b
This compared to the Validator component, where it's a soft requirement.
Is there any hassle-free approach for 4.x or 5.0 here? (in an effort to move it to require-dev instead).
The text was updated successfully, but these errors were encountered: