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

Since Symfony 4.2 php syntax errors are not shown, "Expected to find class..." instead #35681

Closed
samuelvi opened this issue Feb 12, 2020 · 4 comments

Comments

@samuelvi
Copy link

samuelvi commented Feb 12, 2020

Hi,

Since Symfony 4.2 when a syntax error happens, this is not shown anymore, instead "Expected to find class..." is displayed.

I tested this behaviour creating an empty project for different Symfony versions and I realized that this happens since SF 4.2. In SF4.1 the right error is displayed.

It makes an error a bit difficult to fix if no deeper info about the error is displayed :)

I hope you can give me a hand on this, thanks a lot!

@linaori
Copy link
Contributor

linaori commented Feb 12, 2020

Sounds like this: #35256

Should be fixed in the next releases of 3.4, 4.4 and 5.0 I think.

@samuelvi
Copy link
Author

samuelvi commented Feb 12, 2020

Tried this morning from a new SF 4.4.4. and SF 5.0.4 project, creating a dummy class with a syntax error and insteaf of getting the syntax error message the error page always shows "Expected to find class...".

It has nothing to do with wrong namespaces neither duplicated services.

Thanks!

@linaori
Copy link
Contributor

linaori commented Feb 12, 2020

Tried this morning from a new SF 4.4.4. and SF 5.0.4 project, creating a dummy class with a syntax error and insteaf of getting the syntax error message the error page always shows "Expected to find class...".

As I said, the fix is not released yet, see: #35557. You can try this locally to see if this fixes the error you're experiencing.

It has nothing to do with wrong namesces neither duplicated services.

The issue I linked is a symptom, not the cause. The cause is most likely the same as in my issue.

@xabbuh
Copy link
Member

xabbuh commented Feb 12, 2020

closing as explained by @linaori

@xabbuh xabbuh closed this as completed Feb 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants