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

Please update to use newer parser version #155

Closed
yellow1912 opened this issue Oct 16, 2013 · 14 comments
Closed

Please update to use newer parser version #155

yellow1912 opened this issue Oct 16, 2013 · 14 comments
Assignees

Comments

@yellow1912
Copy link

To solve php 5.5 syntax issue: nikic/PHP-Parser#76

@tristanbes
Copy link
Contributor

any updates on this 🆙

@Markcial
Copy link

+1

3 similar comments
@ickbinhier
Copy link
Contributor

+1

@nurikabe
Copy link
Contributor

+1

@billmccord
Copy link

+1

@sagikazarmark
Copy link

Depending on one fixed version collides with other packages. Please upgrade to a higher package and use a version constraint. The latest release (1.4.1) is far from the required one (0.9.4)

@sagikazarmark
Copy link

Duplicates: #244, #255

PRs: #176, #246

@respinoza
Copy link

+1

@jeffclemens
Copy link

The master version is using parser v1+ however the 1.1.0 release still points to parser v0.9.

@benjamin-hubert
Copy link
Collaborator

Released in 1.2.0

@kacperk83
Copy link

The issue still occurs in version 1.2.0. Also still in FormExtractor.php but this time on line 173:

Notice: Undefined property: PhpParser\Node\Expr\ArrayDimFetch::$items

Temporary fix:

prepend condition with isset($item->value->items).

@Nyholm
Copy link
Collaborator

Nyholm commented Apr 5, 2016

The issue still occurs in version 1.2.0

@kacperk83: What issue? In 1.2.0 we allow you to use the latest version of the PHP parser. If you have experiencing problems with the JMSTranslationBundle that is not related to this topic feel free to create a new issue and the community will be happy to assist you.

@kacperk83
Copy link

I will do so. Thank you.

@gnat42
Copy link
Collaborator

gnat42 commented Apr 5, 2016

The second bug he reported is still there. The $items one PR #339 fixes it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests