PhpParser | PHP language parser with pure PHP | Parser library

This is a lot more complicated than other questions you've asked, but it has been interesting to learn about how to write it.

I've put comments through the code, but basically it analyses the code and looks for assignments (instances of PhpParser\Node\Expr\Assign nodes). It then splits it into left and right parts and recursively extracts any variables in either parts.

The code allows for nested variables on either side of the expression, I've changed the example code to provide some broader examples.

Comments in code (assumes some knowledge of how the parser works with nodes etc.)...

consume is not a rule defined in the PHP grammar. Try this:

Since you don't show any of your grammar, it's not possible to provide a specific answer. Also I really don't know enough about the PHP runtime for Antlr to more than hazard a guess at what this does:

This should work for the particular instance you have highlighted, it only does the POST instance, but that should be easy to expand.

The main part is when you see the AST for the code, try and make sure you can identify the base of the _POST access. This turns out to be a Node\Expr\ArrayDimFetch, then inside this you want to check if the variable it is using is _POST.

Once you have identified this, you can replace that node with a new one which is just a string Node\Scalar\String_("Hello World!");.

Turns out that I was missing a package. @EquaPro pointed out in the comments that PhpParser is a part of doctrine/common package, which isn't installed by any of the packages I have in my composer.json.

Possible reasons: when I was following the Security/Authentication tutorial, I decided to not install Doctrine since I wasn't going to use it.Fixed it by installing symfony/orm-pack.

Since you're using Argon2i as the encoder algorithm for your entity, your $salt becomes obsolete:

Do you need to use a Salt property?

If you use bcrypt or argon2i, no. Otherwise, yes. All passwords must be hashed with a salt, but bcrypt and argon2i do this internally [...] the getSalt() method in User can just return null (it's not used). [...]

-How to Load Security Users from the Database (the Entity Provider)

Try removing the $salt property and the setter method, and let your getSalt() return null. Persist the user without encoding operations and check the persisted password.

While this can be seen as a dirty hack, it seems to be a good practice...

You can try this,