Skip to content

[ExpressionLanguage] Fix LexerTest number types #44088

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

Merged
merged 1 commit into from
Nov 17, 2021

Conversation

fancyweb
Copy link
Contributor

Q A
Branch? 4.4
Bug fix? no
New feature? no
Deprecations? no
Tickets #44073 (comment)
License MIT
Doc PR -

Very minor but it's better like this.

@fancyweb fancyweb force-pushed the el/fix-lexer-test-number-type branch from 495531e to bdf9adc Compare November 16, 2021 18:00
@fancyweb
Copy link
Contributor Author

I'm taking the opportunity to add tests for the range operator with actual numbers because there are none. My initial implementation in the other PR fails for them but I did not notice it until now because there were no tests.

@fabpot
Copy link
Member

fabpot commented Nov 17, 2021

Thank you @fancyweb.

@fabpot fabpot merged commit 52d0a50 into symfony:4.4 Nov 17, 2021
@fancyweb fancyweb deleted the el/fix-lexer-test-number-type branch November 17, 2021 08:03
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.

4 participants