Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
[Yaml] Making the parser stateless#45140
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
carsonbot commentedJan 23, 2022
Hey! I see that this is your first PR. That is great! Welcome! Symfony has acontribution guide which I suggest you to read. In short:
Review the GitHub status checks of your pull request and try to solve the reported issues. If some tests are failing, try to see if they are failing because of this change. When two Symfony core team members approve this change, it will be merged and you will become an official Symfony contributor! I am going to sit back now and wait for the reviews. Cheers! Carsonbot |
stof left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Looking at the properties, the reset is also missing forrefsBeingParsed
mamazu commentedJan 24, 2022
This is true and on some objects the offset is getting reset back to 0. I haven't really dug into the code of the parser. |
mamazu commentedJan 24, 2022
Should I also add a reset for the |
nicolas-grekas commentedJan 24, 2022
Yes please |
fabpot commentedJan 25, 2022
Thank you@mamazu. |
Currently if you parse multiple files with the same
Parserinstance, you get different results in the error reporting since the parser doesn't reset the offset.How to reproduce
If you remove the line added in the parser then the error message shows the incorrect line number and the test will fail.