Skip to content
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

[Form] Support customized intl php.ini settings #36149

Merged
merged 1 commit into from Mar 23, 2020

Conversation

jorrit
Copy link
Contributor

@jorrit jorrit commented Mar 20, 2020

Q A
Branch? 3.4
Bug fix? yes
New feature? no
Deprecations? no
Tickets no
License MIT
Doc PR no

IntlDateParser->parse() behaves differently when intl.error_level and/or intl.use_exceptions are not 0.

This change makes sure \IntlException is caught when intl.use_exceptions is 1 and warnings thrown when intl.error_level is not 0 are ignored.

@jorrit jorrit requested a review from xabbuh as a code owner March 20, 2020 12:13
@jorrit jorrit changed the base branch from master to 5.0 March 20, 2020 12:34
@jorrit jorrit force-pushed the intlinisettings branch 2 times, most recently from ddc608e to 251aa20 Compare March 20, 2020 12:54
@nicolas-grekas nicolas-grekas added this to the 3.4 milestone Mar 20, 2020
@nicolas-grekas nicolas-grekas changed the title Support customized intl php.ini settings [Form] Support customized intl php.ini settings Mar 23, 2020
@nicolas-grekas nicolas-grekas changed the base branch from 5.0 to 3.4 March 23, 2020 12:03
`IntlDateParser->parse()` behaves differently when `intl.error_level` and/or `intl.use_exceptions` are not 0.

This change makes sure `\IntlException` is caught when `intl.use_exceptions` is 1 and warnings thrown when `intl.error_level` is not 0 are ignored.
@nicolas-grekas
Copy link
Member

Thank you @jorrit.

@nicolas-grekas nicolas-grekas merged commit 5b5b61f into symfony:3.4 Mar 23, 2020
@jorrit
Copy link
Contributor Author

jorrit commented Mar 23, 2020

No problem @nicolas-grekas, thanks for merging!

@jorrit jorrit deleted the intlinisettings branch March 23, 2020 12:08
This was referenced Mar 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants